Hello,
I'm not the best at flashing and all that, and I'm sure I'm doing something wrong here:
I have the problem like many, there is a 2cm bar over top of the screen where my touch is not responding, sometimes it works, sometimes not. Some say to zap it with a lighter's spark, tried it, didnt manage to do anything; others said custom ROM solves it.
(if you know a fix I'm not aware of, feel free to post).
From the "LineageOS" topic on the Elephone forums it says I need Android 6.0 (tried with 7.0, just to try -> bootloops),
the problem is I cant manage to get 6.0 working on my phone, I flash it with SPFT and when it says its done, my phone doesnt turn on, doesnt charge and does nothing. The only way to get it up and running is to flash stock ROM while holding VOL+ and plugging it in.
What am I doing wrong? Am I misunderstanding the steps? Am I just plain dumb? (probs)
If you need any more info, please ask.
Thanks fellas.
Update:
If I understood corectly you cant downgrade because the bootloader gets also updated to and doesnt allow downgrading if not unlocked, so I went and tried to unlock OEM.
It all works fine and dandy until I get to the "Press Volume UP to unlock or Volume DOWN to cancel" part, when I press UP nothing happens, and when I press DOWN it just cancels.
TWRP is flashed, and is rooted.
VirusWar said:
Update:
If I understood corectly you cant downgrade because the bootloader gets also updated to and doesnt allow downgrading if not unlocked, so I went and tried to unlock OEM.
It all works fine and dandy until I get to the "Press Volume UP to unlock or Volume DOWN to cancel" part, when I press UP nothing happens, and when I press DOWN it just cancels.
TWRP is flashed, and is rooted.
Click to expand...
Click to collapse
Thats wrong, this device comes unlocked by default, which is why you are able to boot twrp.. The reason the device doesnt boot when you try to downgrade is because the preloader is too old, you need to go to the lineage 13 forum and download the preloader tool provided there and flash it, alongside lineage 13 flash it from twrp, it should be android 6, you can still go to android 6 stock rom if you flash stock rom and then the preloader provided in the lineage (the most resent preloader for the 6.0) u should get android 6 stock booting
Thanks for clearing things up, it worked.
Sadly, it didnt fix the touch screen problem, I guess its faulty or something like that, I'll replace it when I've got the funds.
Thanks for the help.
Related
Hello!
It's insane, here is the description.
The android booted up just in safe mode.
The winmo had faults, so I've decided to change the whole system, with task 29.
At first I've changed my radio to the 2_12_50_02_2 version.
Than I've started the task29, the one what do not needs the radio.
Thats all I've done, and now I cannot reach the boot loader, or anything else.
The vol up and start trick is not working.
Please give me a solution, I need this phone working, I need a solution, and I appreciate every tip.
Thank You in advance!!!!
its volume down, not up.
same problem for me here
i did task29 and it was all fine, 100% reached and then the HD2 did a reboot, stopping at the black screen with the white HTC logo.
then as always i removed the battery and put it in again, holding vol down und clicking power-up once.
nothing happend... the phone vibrated once and got back to the HTC logo.
NO bootloader!
please do not tell me i'm too dumb to enter bootloader, i've been flashing custom roms for 6 months now!
my latest rom was Goatrip 6.0 and HSLP is 2.08
yesterday when goa6 was still "alive" the volume-down button worked fine, so the problem cant be some dust or dirt beneath the buttons.
edit: i've also tried flashing via SD card (clean FAT32 formatted 2gb card) the original stock rom 3.14 and a custom rom,
none of them is working either
every single hint of how i could solve this issue would be great!
hope to here from u guys
Remove the SD card and try again to go into BootLoader mode.
i have tried all methods and variations but i cant enter bootloader...
now i have found this thread:
--eeeeek cant post links --
its referring to the TP2 but i thought i would give it a try!
i've done this sketchy voldown+power+usbcable+batteryplugin thing but no result, even after 10 attempts :-(
Since you removed the battery, are all the pins straight?
those 5 (2 1 2) pins are in good shape
i cant post a link yet, ill send it to u via PM
posting links enabled:
http://forum.ppcgeeks.com/htc-touch-pro-2/122134-task29-didnt-complete-cant-enter-bootloader.html
i got it!
my stepfather owns a HD2, too.
i plug mine into his docking station while i was on the phone with htc support... just because i was bored waiting in the queue.
after the phone call i tried once again to enter bootloader e voila => boooom 3 colour screen!
i dont know whats the reason for, but i flashed my custom rom as fast as i could and it works fine.
but even now i cant enter bootloader properly...for 10 times trying 2 times actually work!
in the WM Os its no problem, Vol-Down functionality is 100%
cant explain that to me,
i think u need some luck to get this issue solved
___EDIT___
now with my customrom i could easily enter the bootloader via software command
and therefore i downgraded HSPL to stock spl1.42.000.
after this i flashed 2.08.hspl again and NOW my bootloader is working as intended!
u see, once u can get into bootloader again, all your problems can be fixed.
without him, you're f*cked
greetings
I recently bricked my tablet after having it rooted for a very long time...a Samsung-issued update apparently screwed with something crucial.
Anyway, I tried the nvflash recovery methods as mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1130574
However, it seems that I have what they called a "locked" tablet. I get the 0x4 error he mentions and absolutely nothing happens when I send the command in nvflash.
Is there any update on this recovery method with locked tabs? I tried seeking paid services where they hook up devices to a JTAG and whatnot, but I've only seen that for the original Galaxy and not the 10.1--if you have any information about that route, that would help too.
Thanks!
you can try flashing a old rom if you can thats what i did and it worked for me
samwest39 said:
you can try flashing a old rom if you can thats what i did and it worked for me
Click to expand...
Click to collapse
The thing is I can't flash to different ROMs or even get the Tablet to boot up into download mode...
go to recovery mode
I can't get into recovery mode too. All of the partitions are screwed, and the only way of reviving this device is by flash through the NVidia Recovery Console (nvflash). The thing is, my device is one of the lucky ones that are locked..Thus, it requires a special key to unlock it before I can do anything in nvflash.
I have no idea if this would work, but you could try it ...
A few months ago I was flashing a ROM on a friends phone and something went wrong, the phone wouldn't even boot up any more, the screen stayed blank all the time, no matter which combination of buttons I pressed of how long I held them down for. ODIN didn't recognise it being connected to the PC etc... nothing worked.
Then I tried hooking the phone to the PC again and tried to do something with adb. And somehow, the phone was connected on adb. Tried an adb restart-to-download command and after a minute or two, the phone booted up and I could flash through ODIN again.
I have no idea why it worked, but it did ... lucky me .
So while I doubt it will work, it might still be worth a try. And if adb connects in any way you could maybe figure what was wrong and somehow fix it?
I also heard about some phones being locked out in a similar way and a procedure in the lines of "take the battery out, hold down 3 buttons, slide the battery in WHILE STILL HOLDING the buttons" worked, maybe there's something similarly "hidden" on the tab?
I hope you find your answer!
Hi everyone,
I am having a strange issue here. I updated to MM Beta using the Local Update Method. Update went fine, told me everything was ok.
Well, as soon as the screen turned on, I noticed that nothing was ok. The Honor logo appears, then it goes to System boot and stays there.
I didn't unlock the bootloader neither did I root it, which means everything is still original.
My problem now is, I can't do anything in the sense of:
Not possible to do a rollback, Install Fails
Not possible to install a Full Official Firmware UPDATE.APP, Install Fails
Not possible to use fastboot to flash images of course since I did not unlock it
Not possible to use the USB HiSuite Recovery method (Connect to USB and power on while pressing volume+) because it reboots instantly after showing me the "Download Update" button
I tried with several different Versions of the Firmware for PLK-L01, but nothing seems to work.
I already wrote an email to the Honor Support, but of course it will take time to answer and I don't have any other phone right now.
Should I unlock the bootloader by using the Code generated by the Huawei Website? If yes, how can I retrieve the information if the phone is not booting?
Or should I do something else?
It looks like nobody was or is in the situation I am, because everyone was able to resolve. I tried already everything that I could search and think of.
I appreciate if someone takes the time to help me since I ran out of Ideas.
And of course
Merry Christmas to everyone
Well I called support, and of course they want me to send them the phone.
Does anyone have experience in flashing the extracted firmware directly to the phone?
If I am able to unlock the bootloader, is it worth it trying? Or am I going to screw up stuff even more?
unlocking the bootloader may not help you* - and if you're sending it back, it will help you even less!
you can only flash boot, system and user from Huawei bootloader, it's a sh!t bootloader to be honest, you'll have modem and other bits from the MM flash.
did you place the rollback onto an sdcard in a directory called "dload", insert the card then do the "three button combo"?
turn it on holding vol + / vol - and power, keeping them held until the firmware updater is displayed - it should then force the downgrade.
this leaves you with an unusable phone so you then need to place the UPDATE.APP from B121** in this same sdcard directory and do the same again
You can then do B121-B140 via local update on the working phone..
* - actually unlocked bootloader saved me, flashed B121 system and user and rollback package worked
** - possibly B100 and work your way up
sminki said:
unlocking the bootloader may not help you* - and if you're sending it back, it will help you even less!
you can only flash boot, system and user from Huawei bootloader, it's a sh!t bootloader to be honest, you'll have modem and other bits from the MM flash.
did you place the rollback onto an sdcard in a directory called "dload", insert the card then do the "three button combo"?
turn it on holding vol + / vol - and power, keeping them held until the firmware updater is displayed - it should then force the downgrade.
this leaves you with an unusable phone so you then need to place the UPDATE.APP from B121** in this same sdcard directory and do the same again
You can then do B121-B140 via local update on the working phone..
* - actually unlocked bootloader saved me, flashed B121 system and user and rollback package worked
** - possibly B100 and work your way up
Click to expand...
Click to collapse
Yes, did it. It always says Failed to Update.
Neither the rollback, nor a complete Firmware works. I really don't know what to do.
On the phone they told me that it is normal that this happens, so I am quite questioning the quality of the Update service of Huawei Honor.
Still they want to cover it over the Warranty, but it will take a lot of time. And I seriously need a phone ASAP.
Any other advices maybe?
Thanks for the support anyway :good:
So, I was able to get my phone to boot back by unlocking the bootloader and flashing the B100 Firmware (Like described here)
The phone booted finally, the only problem is the Sim card not being recognized, probably because of the MM MODEM.
Now I will try to flash another full Firmware to see if I am able to get the modem back.
Otherwise I was thinking of flashing the TWRP recovery and creating myself a flashable MODEM from the UPDATE.APP of the B100. Will that work or is it influenced from the bootloader too?
the bootloader has limited end-user commands i don't think you will be able to flash "modem"
sminki said:
the bootloader has limited end-user commands i don't think you will be able to flash "modem"
Click to expand...
Click to collapse
Thank you, I was able to recover my phone completely in the end with a different approach.
I just used and flashed the B130 Full Firmware through the Vol+ Vol- Power combination. Even though it said it failed, it actually works flawlessly. The phone works even better than before.
I was scared I would not be able to recover it, but with an unlocked bootloader and the right tools, everything is possible.
So thank you again @sminki, and thanks to all of the XDA Forum members who published tools like Huawei Update Extractor and the single firmware files.
:good::good::good::highfive:
that's great news, welcome back!
Here's how it started:
I was happily using the tablet (pollux_windy), when something prompted me to upgrade to 7.11 Lineage OS images. One of the things noteworthy here is that I was never able to go to recovery by pressing VOLUME_UP. I was always using adb to reboot to recovery
I installed it and used OpenGapps aroma installer to install what I wanted. I removed a few CM account related stuff
The tablet booted but was being stuck on the first screen on initial setup that displays a big LineageOS logo in green and there was no other option on it. I thought maybe the tablet is being slow and left it overnight to see if anything appears. Nope.. nothing did.
I tried a lot to go to recovery to reflash or flash something good. But as I mentioned before, I wasn't able to get into recovery by key combinations.
I tried to use Sony Companion to do a Software Repair. It kept complaining that bootloader was unlocked
I tried to use flashtool on mac to flash a stock FTF. It kept giving error (ERROR - null, ERROR - Error flashing. Aborted)
Since it looked like the only problem with using Sony Companion was that bootloader was unlocked. So I proceeded to lock the bootloader from flashtool. I believe this was where I messed up. I locked it successfully
I then proceeded to use software companion but it keeps giving me error with a small message about UEGetPhoneInfoFailure. I searched a few forum and posts but it seems that there's no solution for this (?)
I tried to unlock my bootloader again. I did it through the official method the first time and repeated it but fastboot write failed and it wasn't unlocked. Flashtool is not able to unlock it as well. Flashtool error is (Your phone bootloader cannot be officially unlocked)
I tried various versions of flashtool in MacOS and in Windows, trying to flash any FTF. I get a new error along with the one I mentioned above (-: Processing of loader.sin finished with errors)
I'm now typing this post
I'll appreciate if someone can help here.
I got this device when it first came out. I've loved it since now. It was an ace. It's not waterproof anymore because I did a few repairs on my own. But it worked flawlessly and battery life was great. I wouldn't mind saying goodbye to it as it's pretty old, but trying to revive it and have it living as it's cooler than a dead tablet
kishu27 said:
I'll appreciate if someone can help here.
Click to expand...
Click to collapse
Don't panic!
7.1.1 ROMs have some issues when reverting back to stock ROM.
Switch off device by holding VOL+Power for 5-7 sec, then read -> https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Rootk1t said:
Don't panic!
7.1.1 ROMs have some issues when reverting back to stock ROM.
Switch off device by holding VOL+Power for 5-7 sec, then read -> https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Click to expand...
Click to collapse
One thing I always practice and preach about Sony devices is not to panic .. Flash mode and Flashtool has saved my a** so many times.
So, thanks to you, I resolved the issue. I was doing the same thing but had a couple of pieces in the process that needed correction.
I let go of my Windows VM on Mac and prepped my old laptop fresh on Windows 10. Driver installation kept failing because of unsigned driver issue and bcdedit didn't do anything despite returning a success. Advanced startup worked. The second thing that might be wrong with my original attempt was the stock FTF version. 5.1.1 didn't work. I got hold of a german unbranded version on 4.1.2 and used it instead. Then reflashed to 5.1.1 and everything is golden.
Thanks again :good:
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.