我的手机amaze,已经官方解锁了,super-cid写入失败,从新写入系统时,失败了。可是电脑端显示成功,我重启手机,手机开不开机,也进不去HBOOT,屏幕只能显示四角各有个感叹号,中间一个灰色的'HTC'的字样,怎么办求解!知道答案的请发 Edited by Moderator.
——————我是一个中国学生!翻译不好请见谅!—————————————————————————————————————————
My mobile phone amaze, have unlock, super-cid write failure, from the new writing system, failed. But the computer terminal display success, I restart mobile phone, mobile phone to open the boot, cannot also go in the HBOOT, the screen shows only four corners of an exclamation point, the middle of a grey 'HTC'', how to do to solve! Know the answer please Edited by Moderator. Mr. lu! Thank you very much.
boxboooon said:
我的手机amaze,已经官方解锁了,super-cid写入失败,从新写入系统时,失败了。可是电脑端显示成功,我重启手机,手机开不开机,也进不去HBOOT,屏幕只能显示四角各有个感叹号,中间一个灰色的'HTC'的字样,怎么办求解!知道答案的请发 [email protected] 卢先生!谢谢你们!
——————我是一个中国学生!翻译不好请见谅!—————————————————————————————————————————
My mobile phone amaze, have unlock, super-cid write failure, from the new writing system, failed. But the computer terminal display success, I restart mobile phone, mobile phone to open the boot, cannot also go in the HBOOT, the screen shows only four corners of an exclamation point, the middle of a grey 'HTC'', how to do to solve! Know the answer please [email protected] Mr. lu! Thank you very much.
Click to expand...
Click to collapse
当你用4个惊叹号宏达屏幕上,尝试做此命令
fastboot devices
然后让我们知道,如果你看到什么
___________________________________
When you are on the HTC screen with 4 exclamation marks, try to do this command
fastboot devices
and then let us know if you see anything
Sorry if the chinese is bad, I'm using google translate
Keylogger_0 said:
当你用4个惊叹号宏达屏幕上,尝试做此命令
fastboot devices
然后让我们知道,如果你看到什么
___________________________________
When you are on the HTC screen with 4 exclamation marks, try to do this command
fastboot devices
and then let us know if you see anything
Sorry if the chinese is bad, I'm using google translate
Click to expand...
Click to collapse
Unable to access FastBoot,Only one interface
boxboooon said:
Unable to access FastBoot,Only one interface
Click to expand...
Click to collapse
Did you plug in usb cable? Do you have fastboot drivers installed on the computer?
Keylogger_0 said:
Did you plug in usb cable? Do you have fastboot drivers installed on the computer?
Click to expand...
Click to collapse
I don't have this mode drive, only HTC sync. Oh, God, my mobile phone is dying! Can only send HTC to repair? Though I know I repaired the possibility is very small, but I am very grateful to you Keylogger_0! Thank you. Thank you XDA!
谢谢Keylogger_0!祝你健康快乐~
boxboooon said:
I don't have this mode drive, only HTC sync. Oh, God, my mobile phone is dying! Can only send HTC to repair? Though I know I repaired the possibility is very small, but I am very grateful to you Keylogger_0! Thank you. Thank you XDA!
谢谢Keylogger_0!祝你健康快乐~
Click to expand...
Click to collapse
You don't need to send to HTC for repair. More likely than not, we can fix it. If not, then yes, you send to HTC.
Okay, I can't read chinese, which makes things difficult.. but all the answers will require the user to be able to read some english anyways, so...
First: What did you do before the issue happened? Did you try to install the RUU? Were you going for s-off? What EXACTLY did you do before the issue.
Second: What happens when you turn on the phone while holding the down volume button? The feedback I see from people having this issue, it seems most are able to access the bootloader..
Third: Did you google "4 exclaimation marks htc"? There are a LOT of answers out there that may help you, and I have yet to find anything that says your device is bricked..
As this is the first time I have seen someone have your issue the most important question is "WHAT DID YOU DO BEFORE ISSUE".. so we can make sure people do NOT do that! The community can probably help if you can work around the language barrier a bit.
Silentbtdeadly said:
Okay, I can't read chinese, which makes things difficult.. but all the answers will require the user to be able to read some english anyways, so...
First: What did you do before the issue happened? Did you try to install the RUU? Were you going for s-off? What EXACTLY did you do before the issue.
Second: What happens when you turn on the phone while holding the down volume button? The feedback I see from people having this issue, it seems most are able to access the bootloader..
Third: Did you google "4 exclaimation marks htc"? There are a LOT of answers out there that may help you, and I have yet to find anything that says your device is bricked..
As this is the first time I have seen someone have your issue the most important question is "WHAT DID YOU DO BEFORE ISSUE".. so we can make sure people do NOT do that! The community can probably help if you can work around the language barrier a bit.
Click to expand...
Click to collapse
1:问题发生前,我在试图写入“super-cid” 但是写入失败,原因是没有s-off。在这时,手机的情况是:官方解锁,没有s-off。
2:打开手机,按住下音量按钮时,就是图上的那样,无法进入hboot
提醒别人不要用线刷的方法将官方的zip解锁包第二次刷入官方解锁的手机了!因为这样做会使字库里的数据被擦掉却没有再次写入!
我是学生,现在开学了,回复很慢见谅~
1: problems before they occur, I was trying to write " super-cid " but write failed, because there is no s-off. At this time, the mobile phone is: unlock, no s-off.
2: open mobile phone, press and hold the volume buttons, is a map of it, can not enter the HBOOTRemind the others do not use wire brush method will be the official zip unlock the package second brush into the official unlocked mobile phone! Because it will make in the font data erased but not write again!I am a student, school now, the reply is very slow. ~
boxboooon said:
1:问题发生前,我在试图写入“super-cid” 但是写入失败,原因是没有s-off。在这时,手机的情况是:官方解锁,没有s-off。
2:打开手机,按住下音量按钮时,就是图上的那样,无法进入hboot
提醒别人不要用线刷的方法将官方的zip解锁包第二次刷入官方解锁的手机了!因为这样做会使字库里的数据被擦掉却没有再次写入!
我是学生,现在开学了,回复很慢见谅~
1: problems before they occur, I was trying to write " super-cid " but write failed, because there is no s-off. At this time, the mobile phone is: unlock, no s-off.
2: open mobile phone, press and hold the volume buttons, is a map of it, can not enter the HBOOTRemind the others do not use wire brush method will be the official zip unlock the package second brush into the official unlocked mobile phone! Because it will make in the font data erased but not write again!I am a student, school now, the reply is very slow. ~
Click to expand...
Click to collapse
Download this attachment, extract it to desktop, and then run Vars.bat file and attach the file DIAGNOSTIC.LOG when its done
Don't forget to attach the file 'DIAGNOSTIC.LOG' which will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
_______________________________________
下载这个附件,解压缩到桌面,然后运行Vars.bat文件和附加文件DIAGNOSTIC.LOG时
不要忘记附加文件“DIAGNOSTIC.LOG”这看起来像这样:
Edit: English was included. Thread open.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice
Sent from my HTC One X, using XDA Premium
http://forum.xda-developers.com/announcement.php?a=81
I'm still willing to help, especially when someone has a unique problem.. I think it would be helpful to know what he did before the issue happened, that would help more in troubleshooting or keeping the issue happening for others. This is the first time I've seen someone with this issue.
Sent from my HTC_Amaze_4G using xda app-developers app
Related
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
The cm team can help you on IRC here's info I copied from the cm thread go here and they should get you right http://webchat.freenode.net?channels=cyanogenmod-touchpad
The reason the doctor is failing is because Android messes with your partitions and at 12% the webOS doctor is verifying partitions. Have you attempted ACMEUninstaller? When at the webOS screen go ahead and run ACMEUinstaller. Then if uoi can boot into webOS do the complete wipe to wipe the entire SD section. Then doctor it and then reflash Android with ACMEinstaller2
Sent from T the Touchpad
Eat it iPhone said:
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
lucky for us, the TP can never be bricked unless you start to manually edit partition tables (and even then, its fixable with much hair pulling, ive personally troubleshooted this with a friend before )
maybe these threads can help you out:
http://forum.xda-developers.com/showthread.php?t=1236727&page=2.
http://forum.xda-developers.com/showthread.php?t=1379579
it really helps to have a grasp on how novaterm works, and ALWAYS ALWAYS re read your commmands to ensure you typed it correctly (upper/lower case espicially ;P)
Thx guys ill look into it, but I'ma be busy so ill have to chk this out tomorrow
Sent from my PG86100 using XDA App
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
rr5678 said:
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
Click to expand...
Click to collapse
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Solidus_n313 said:
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Click to expand...
Click to collapse
It may be horrible but in the end it's worth it
P.S.: I read that link in your signature (The TRUTH: XDA: Then and Now), and all I have to say is.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
darkassain said:
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
Click to expand...
Click to collapse
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
rr5678 said:
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
Click to expand...
Click to collapse
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
darkassain said:
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
Click to expand...
Click to collapse
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
rr5678 said:
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
Click to expand...
Click to collapse
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
darkassain said:
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
Click to expand...
Click to collapse
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
rr5678 said:
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
Click to expand...
Click to collapse
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
darkassain said:
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
Click to expand...
Click to collapse
I wish it was known what to do though. That's a super low level function.
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
mike4peace said:
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
Click to expand...
Click to collapse
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
palmbeach05 said:
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
Click to expand...
Click to collapse
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
You also need drivers.
All of that has been covered already. Did you search?
ravilov said:
You also need drivers.
All of that has been covered already. Did you search?
Click to expand...
Click to collapse
yes mate i have motorola device manager, as far as i know this the same thing right? just like samsung's kies
i really did tons of search but im almost hopeless. guys who have the same problem did solved it by just taking device to fastboot but mine is not going in that mode. when i plug the device its charger it says same problem and also says battery too low to flash. so im just gonna go and buy a new battery
mike4peace said:
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
Click to expand...
Click to collapse
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
palmbeach05 said:
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
Click to expand...
Click to collapse
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
mike4peace said:
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
Click to expand...
Click to collapse
That's rsd mode, I think. From there you can flash an full sbf and start over
Enviado desde mi MB860
ravilov said:
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
Click to expand...
Click to collapse
not hard brick? oh thank god, i said so because the phone does nothing
yeah i searched it before and its calldd factory cable, i havent done it yet but i tried usb jig which was a failure. no one owns an atrix around me, so i just need a external charger and right now im onto it
guys, i really appreciate your helps, im very glad to have you here thanks a lot. i will post here the results
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
Here is short explanation what hard brick is:
Hard bricks are more or likely that you won’t be able to fix it. If you get a hard brick, your phone will not be repaired, there will be absolutely no way to without sending it to the manufacturer. This could be from wiping the entire system without flashing a rom, no way into recovery and no way to get it back. This could be also caused from bad installation files, or turning off/removing the battery from your device during the first installation or boot up sequence. Sometimes you can fix a hard brick, but more often than not your device is going to be broken. This is a fix that is required by the manufacturer of the device. Honestly if you get this, it may just be simpler to go get the device replaced instead of even trying to fix it. HOWEVER make sure you go out and read about it, typing in the exact problem and doing lots of research for your specific device as there may be some hope for the device somewhere.
Click to expand...
Click to collapse
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
palmbeach05 said:
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
Click to expand...
Click to collapse
im not quite sure cause i bought this phone intentionally via ebay-like web site
yanick76 said:
Here is short explanation what hard brick is:
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Click to expand...
Click to collapse
okay soft brick it is, but my phone doesnt do anything but show an error screen (and goes)
andresrivas said:
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
Click to expand...
Click to collapse
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
mike4peace said:
[...]
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
Click to expand...
Click to collapse
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
andresrivas said:
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
Click to expand...
Click to collapse
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
mike4peace said:
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
Click to expand...
Click to collapse
JTAG depends heavily on your ability to solder tiny surface mount components. Good luck.
Hello there experts,
The volume buttons of my S2 don't work at all. I bought it 2nd handed and the seller told me this beforehand. It seems they were broken in the process of replacing the screen, God knows who made such mistake.
I installed cyanogenmod with CM installer, as it does the job almost automatically without the need to go to the Download mode.
Once everything was installed and set up I thought, well let's try to remove that yellow triangle image...
After installing Triangle Away, it brought me to the download mode. I knew it was risky but I thought the phone would restart normally.
If I remove the battery, it'd always go back to download mode, and there is no way to start the phone normally.
as I'm unable to either press VOL up / down, i'm stuck in the download mode.
The only solution that comes to mind is disassembling the phonem, play with the volume buttons and see what's happening there, and try to fix it (if there's even a possible fix)
Does that look like it could be fixed? or it would need to replace and solder something else?
also, is there a way to get rid from the DL mode with some USB method on the PC? also flashing the phone as it is right now is impossible I guess.
this is what I found in the volume parts,
it's the first time I dare to disassemble a device like this. I have no clue about this kind of stuff;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try ADB Fastboot commands. Maybe it detects S2 in Download Mode. But not sure about that. First of all,
Download Samsung USB Drivers.
Download Minimal ADB & Fastboot
Connect USB Cable
Open that command line tool
Issue command 'adb devices' or 'fastboot devices'. If it detects your phone, your IMEI will be shown. Then try,
ADB Fastboot Reboot System
If all good, your S2 will be rebooted.(presuming that you're Rooted). If it doesn't you have to repair those keys or try to press them by some sort of sharp thing but easy you go, otherwise you will be damaging your phone. I recommend you ti get them repaired
syedbilal093 said:
Try ADB Fastboot commands. Maybe it detects S2 in Download Mode. But not sure about that. First of all,
Downliad Samsung USB Drivers.
Download Minimal ADB & Fastboot
Connect USB Cable
Open that command line tool
Issue command 'adb devices' or 'fastboot devices'. If it detects your phone, your IMEI will be shown. Then try,
ADB Fastboot Reboot System
If all good, your S2 will be rebooted.(presuming that you're Rooted). If it doesn't you have to repair those keys or try to press them by some sort of sharp thing but easy you go, otherwise you will be damaging your phone. I recommend you ti get them repaired
Click to expand...
Click to collapse
Thanks for your help.
Yes I was root, the solution you gave looks like it could have worked to get rid from the download mode.
Anyways, the flex that connects the buttons internally was broken, maybe this was a good thing that had to happen to get it repaired, as sooner or later I'd have to do that.
Finally I found a guy who is a beast at these things and he had lots of parts of S2's, so he repaired it in about 10 minutes.
Now I have a fully functional S2. It's still a good device in my opinion.
I bought it 2nd handed for a lower price that any chinese phone, good cam and speakers... makes me wonder if we should get ex-flagship devices instead of newer chinese cheap phones. I paid only 55euros for this phone, I know it's usually more expensive. After using a chinese android phone, my experience is much better with the S2.
So far I'm using cyanogenmod11 as my first rom. I know this question can be dumb and repetitive, but could you tell me what are the best roms/rom in your honest opinion? As usually, the smoothest running and more lasting battery are the most demanding needs.
Thanks again man!
Thats good to hear that. Yeah chinese phones are not good at all. Samsung S2 is a demanding phone still. I am also using S2.
As you asked about ROMs, personally i haven't rooted my S2. But in my opinion, i am listing three links about Top Custom ROMs. Visit them you'll find something for your S2.
http://www.cnet.com/how-to/best-custom-roms-for-the-samsung-galaxy-s2/
http://androidcure.com/best-kitkat-roms-samsung-galaxy-s-ii-i9100/
http://www.androidpit.com/best-5-custom-roms-for-the-galaxy-s2
Visit CNET first. In my honest opinion, stock Rom is the best ROM if we talk about stability,smoothness & performance. . Visit them you'll be able to find a ONE for your's.
syedbilal093 said:
Thats good to hear that. Yeah chinese phones are not good at all. Samsung S2 is a demanding phone still. I am also using S2.
As you asked about ROMs, personally i haven't rooted my S2. But in my opinion, i am listing three links about Top Custom ROMs. Visit them you'll find something for your S2.
http://www.cnet.com/how-to/best-custom-roms-for-the-samsung-galaxy-s2/
http://androidcure.com/best-kitkat-roms-samsung-galaxy-s-ii-i9100/
http://www.androidpit.com/best-5-custom-roms-for-the-galaxy-s2
Visit CNET first. In my honest opinion, stock Rom is the best ROM if we talk about stability,smoothness & performance. . Visit them you'll be able to find a ONE for your's.
Click to expand...
Click to collapse
I'm not sure about the s2 but in other devices, the stock updated roms+root access have always been the best configuration. Thing is I don't like TouchWhiz much.
Thanks for the info man. I'll check that out.
Enviado desde mi M9Pro mediante Tapatalk
Yeah check them out. No problem man. ! I also dont like TouchWiz. I like HTC Sense.:thumbup:
hi all i have purchased the Lenovo Tab 2 A8-50F and i have tried everything to root it and cant find a custom recovery for it anywhere..
EDIT::: finally got it rooted with twrp go here for a full guide on how http://forum.xda-developers.com/android/development/root-twrp-lenovo-tab-2-a8-50f-mt8161-t3226130 enjoy
can anyone shed any light on the subject..
SPECS:
MODEL: Lenovo Tab 2 A8-50F
CPU: MT8161 QC 1.3ghz 64Bit
DISPLAY: 8inch 1280*800 IPS
MEMORY: LP-DDR3 1GB
STORAGE: 16GB
OS: Android 5.0.2
thanks in advance..
EDIT: i have found the source code here http://support.lenovo.com/us/en/products/tablets/a-series/a8-50-2/downloads/DS102968
if anyone is intrested in jumping on the boat with me and trying to get this rooted let me know..
UPDATE::::
here is how to unlock the bootloader>>> THIS WILL WIPE THE DEVICE TO FACTORY SETTINGS
first enable usb debugging and make sure oem unlock feature is enabled in developer options.
download the minimal adb (attached)... Extract to desktop or wherever and then run MINADB.exe
in the terminal type adb reboot bootloader you will be rebooted to a black screen which says Fastboot Mode....
now in the terminal type fastboot oem unlock
press the up volume button when asked and WAIT
when its done it will show a menu of boot modes dont do nothing and in the terminal just type fastboot reboot
bootloader is now unlocked.. i am still working on rooting i am trying to find a way to dump the recovery and boot partitions but its proving extra difficult due to permission problems..
I'm in the same boat. I tried everything. I don't think there's a method available for this device yet.
well i am working on it i have done alot of work on new devices and manually figured a root method out.. firstly i need to try and find the source code for our tablet then i can try to get an unsecure boot image then other things will follow on from it..
I believe the source code is on lenovo's website. Idk if that's what you're looking for. http://support.lenovo.com/us/en/pro...,_tablet,_workstation_and_thinkserver_support
DeeJay1 said:
I believe the source code is on lenovo's website. Idk if that's what you're looking for. http://support.lenovo.com/us/en/pro...,_tablet,_workstation_and_thinkserver_support
Click to expand...
Click to collapse
exactly what i am looking for
Awesome! Glad to be of assistance. You said you found a manual root method?
DeeJay1 said:
Awesome! Glad to be of assistance. You said you found a manual root method?
Click to expand...
Click to collapse
yes for other devices.. and i am hoping to find a way on this device but first i need a way to get a custom recovery working on it.. mtk droid tools is a handy place to start and its the best i had it wont root it but it sent me here http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 which happens to be an intresting read..
I too read up on that forum, but I'm not that well versed in Android development lol
lol... well its not so straight forward being that our tablet has a mediatek 64BIT processor.. when i owned the htc desire 510 (uk) it was the first phone with 64bit architecture but i was part of the community that managed to get it rooted after some gruelling hard work.. bad news is that this tablet will probably take quite some time crack.. :/ but i am working on it and i will post any progress on rooting it here..
Inside 4ndroid said:
yes for other devices.. and i am hoping to find a way on this device but first i need a way to get a custom recovery working on it.. mtk droid tools is a handy place to start and its the best i had it wont root it but it sent me here http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 which happens to be an intresting read..
Click to expand...
Click to collapse
Inside 4ndroid said:
lol... well its not so straight forward being that our tablet has a mediatek 64BIT processor.. when i owned the htc desire 510 (uk) it was the first phone with 64bit architecture but i was part of the community that managed to get it rooted after some gruelling hard work.. bad news is that this tablet will probably take quite some time crack.. :/ but i am working on it and i will post any progress on rooting it here..
Click to expand...
Click to collapse
I figured the same. Good luck to you, I'll be looking around for any solution, and let me know if I can assist you with anything.
What is this
I ran into this menu on my tablet. Chinese? Lol
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's a factory test mode, tnx to google translate
I'm not able to create the scatter file...
Any luck with this? so frustrating cant get it rooted, cheers
Same here. I have only had my Tab 2 A8-50F for about a week. I am really liking this tablet. For the price it preforms rather well. Only thing keeping me from making a solid decision to keep it is the lack of Root. If I can't root it I might have to start looking for another device
what is so special about this tablet that it wouldnt be able to be rooted? geez.
I am working on a root but its taking longer than normal being the device has 64bit architecture and our chipset is unsupported across most mediatech tools out there oh and the fact it runs lollipop... Instead of thinking there is something special about it try an help yourselves by testing what is already out there and remember most root tools get updated often so keep an eye on them an keep trying until I can come up with something... I am working on it but these things take time when you have a full time job and 2 children t look after... Happy testing an if you find anything you think may help post it here or pm me... ???
Just got this tablet today, updated it from 5.0.2 to 5.1.0
Good device although the latest OTA (Aug 15) has some UI issues/bugs:
Squashes apps in landscape (most evident with Material Design apps like Play Books, Drive)
Completely breaks Lollipops notification bar coloring, just remains Black or changes to White (Google Translate is a good example)
Strangely the Chromecast icon now shows up permanently in any app that has support, never did this before.
Also, I didn't notice before whilst on 5.0.2 but 5.1.0 now has a "OEM unlocking - Allow the bootloader to be unlocked" toggle in the Developer options menu, is this any use?
Deleted
n/m
ok so i have bricked my device hahaha although i have found out how to get it into preloader mode and it shows in device manager as an MT65xx preloader so if someone could follow this guide and backup there boot and recovery images i would be very gratefull and by providing the rom dump i can get mine unbricked and also get root easily..
could someone please do this for me out of good spirit and to help get root who ever follows the guide successfully at the link below and can provide the files i need will get full credit when it comes to releasing root and recovery..
(you must unclip the back off the tablet and remove a metal plate to unplug the battery befopre putting it into preloader/meta mode..
LINK : http://forum.xda-developers.com/showthread.php?t=2540400
thanks
Hello Everyone,
I pray all had a wonderful weekend. I am a frequent visitor to this site and love all the advice and work many of you do. Thanks for all the support this far!
I searched through the forum to see if I could find some similar issues but was unsuccessful at finding it. I currently have the LG V10 (LG-H901) by T-Mobile running 5.1.1. I was able to successfully unlock the bootloader via fastboot. I came across the issue when I tried to install TWRP-2.8.7.1-h901.img. It would go through fine on CMD but just would not go through on the phone. The fastboot menu would boot up strangely (After unlocking the bootloader) with the text all pixelated in a way. You are unable to read the words. The phone works fine. It happened to me on two phones so it must be something that I am doing incorrectly but just can't find it on Google or this forum. I apologize if I messed and and hate to start a new thread if its here but no such luck finding it. Anyone experience this before or might have some advice? Thanks!
latinpride613 said:
Hello Everyone,
I pray all had a wonderful weekend. I am a frequent visitor to this site and love all the advice and work many of you do. Thanks for all the support this far!
I searched through the forum to see if I could find some similar issues but was unsuccessful at finding it. I currently have the LG V10 (LG-H901) by T-Mobile running 5.1.1. I was able to successfully unlock the bootloader via fastboot. I came across the issue when I tried to install TWRP-2.8.7.1-h901.img. It would go through fine on CMD but just would not go through on the phone. The fastboot menu would boot up strangely (After unlocking the bootloader) with the text all pixelated in a way. You are unable to read the words. The phone works fine. It happened to me on two phones so it must be something that I am doing incorrectly but just can't find it on Google or this forum. I apologize if I messed and and hate to start a new thread if its here but no such luck finding it. Anyone experience this before or might have some advice? Thanks!
Click to expand...
Click to collapse
If it happened on two phones. Then it's likely a step you are overlooking. The biggest thing you need to consider when working on a new device is making sure you have ALL prerequisites before flashing, fastbooting, adb, etc.
- Make sure you have LG usb drivers installed, then reboot your PC.
- Install ADB system-wide
- Turn on OEM unlock in your Dev-settings
- Make sure USB debugging in ticked AND you allow always for the connected PC.
Then start here: http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
Read Read Read Read and Read.
I will give this another try when I get home from work. I am pretty sure I did all that was said but like you stated seems I missed a step somewhere. By going through the steps here over again, even though I went through I might have gone through them already, would that cause any damage? If not I will just go through step one all over again. I did not get the instructions from here so I want to start from the very beginning with the link you posted. Thanks!
latinpride613 said:
I will give this another try when I get home from work. I am pretty sure I did all that was said but like you stated seems I missed a step somewhere. By going through the steps here over again, even though I went through I might have gone through them already, would that cause any damage? If not I will just go through step one all over again. I did not get the instructions from here so I want to start from the very beginning with the link you posted. Thanks!
Click to expand...
Click to collapse
@latinpride613
Did u try my KlicKiT tool.... http://forum.xda-developers.com/showthread.php?p=64598329 as long as u have LG v10 driver installed ... See if that work for you.... Check post #3 for instruction how to install.... But basically just one click the tool do the rest for you to unlock BL and install twrp
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That is awesome. I'll give that a shot as soon as I get home. Thank you!
latinpride613 said:
That is awesome. I'll give that a shot as soon as I get home. Thank you!
Click to expand...
Click to collapse
Make sure you did not forget , or it got reset, go into developer settings and enable Oem Unlock, I know 2 people that kept missing this step for a week.
Watcher64 said:
Make sure you did not forget , or it got reset, go into developer settings and enable Oem Unlock, I know 2 people that kept missing this step for a week.
Click to expand...
Click to collapse
Thanks! I've made sure that's been on from the get go. Forgot I had class today so I am waiting to fly outa here to try this out. I will be sure to update this thread with my results. Any other advice is in the mean while is always welcome.
I first checked if all things above were checked off in the Dev options. They both were the Enable OEM unlock and USB Debugging. I then went in and tried the one click. It booted into fastboot fine but when it gets to the point where its suppose install TWRP the phone itself does nothing. CMD executes fine. The phone just stays where the screen tells you some of the fastboot instructions. From some other sites and videos online it suppose to install TWRP and you can boot right into it.
When you restart the phone you get the message that the bootloader is unlocked on the top left corner. I can't get to the recovery to see if it was even installed. Doesn't seem like it was.
This last step is killing me as I know once I get through this I am rooted. I can try doing it step by step again but feel like I will get the same results. Worth a shot anyways.
When I do "adb reboot recovery" I get a dead android with a red exclamation mark.
latinpride613 said:
I first checked if all things above were checked off in the Dev options. They both were the Enable OEM unlock and USB Debugging. I then went in and tried the one click. It booted into fastboot fine but when it gets to the point where its suppose install TWRP the phone itself does nothing. CMD executes fine. The phone just stays where the screen tells you some of the fastboot instructions. From some other sites and videos online it suppose to install TWRP and you can boot right into it.
When you restart the phone you get the message that the bootloader is unlocked on the top left corner. I can't get to the recovery to see if it was even installed. Doesn't seem like it was.
This last step is killing me as I know once I get through this I am rooted. I can try doing it step by step again but feel like I will get the same results. Worth a shot anyways.
When I do "adb reboot recovery" I get a dead android with a red exclamation mark.
Click to expand...
Click to collapse
@latinpride613
Ok try this.....see if this work for you
1. From extracted KlicKiT folder that where ever you saved let say dektop hold shift then right click.... Open cmd command here.
2. Type these three commands in order one by one then enter.
Hope that work for you...[emoji2] let me know ... And seem like twrp didn't install correctly when you try KlicKiT tool.
ted77usa said:
@latinpride613
Ok try this.....see if this work for you
1. From extracted KlicKiT folder that where ever you saved let say dektop hold shift then right click.... Open cmd command here.
2. Type these three commands in order one by one then enter.
Hope that work for you...[emoji2] let me know ... And seem like twrp didn't install correctly when you try KlicKiT tool.
Click to expand...
Click to collapse
This worked!!! Oh man!!! Thank you, so much!! Everyone, I thank you for reading my post and giving me advice. You all are great!
latinpride613 said:
This worked!!! Oh man!!! Thank you, so much!! Everyone, I thank you for reading my post and giving me advice. You all are great!
Click to expand...
Click to collapse
Im glad that work for you Sir.... That's all XDA about.... Giving back and help others members....[emoji106]
You guys are amazing and Ted, I thank you again (As I don't have access to the "Thank you" button quite yet). Already installed my first ROM on my LG V10.
ted77usa said:
@latinpride613
Did u try my KlicKiT tool.... http://forum.xda-developers.com/showthread.php?p=64598329 as long as u have LG v10 driver installed ... See if that work for you.... Check post #3 for instruction how to install.... But basically just one click the tool do the rest for you to unlock BL and install twrp
Click to expand...
Click to collapse
your tool worked for me, thanks.
What Rom is that
latinpride613 said:
This worked!!! Oh man!!! Thank you, so much!! Everyone, I thank you for reading my post and giving me advice. You all are great!
Click to expand...
Click to collapse
Wht Rom Are U Using