Hi guys. Yesterday I flashed my Lenovo A2010 with Ressurection Remix custom ROM and it seems that I deleted some touchscreen calibration data, because a big part of the touchscreen became unresponsive and the few working areas don't work properly. In other words the touchscreen is completely unusable. Flashing with stock ROM does not help. I have full TWRP backup, but cannot restore it, because TWRP works with touchscreen only. Any ideas on how to fix this? Can I restore the TWRP backup with PC without confirmation from the phone or convert it to a flashable ROM image? Or can I re-calibrate the touchscreen somehow? Any help is much appreciated
I did some googling and found articles on restoring TWRP backups with adb and fastboot, but they don't work for me.
The result of command
Code:
fastbootflash nvram nvdata.ext4.win
in fastboot mode is:
target reported max download size of 134217728 bytes
sending 'nvram' (78 KB)...
OKAY [ 0.018s]
writing 'nvram'...
FAILED (remote: download for partition 'nvram' is not allowed
)
finished. total time: 0.031s
and
Code:
adb -d restore nvdata.ext4.win
in recovery mode says:
Now unlock your device and confirm the restore operation.
which unfortunately I'm unable to do because of the unresponsive touchscreen...
The more I read the more I realise that I flashed ROM for another device and the touch screen driver suplied wrong voltage to the right place and burnt something... So I will assume I have a hardware problem and will close the thread.
Same hear
Please help as the stupid rr room has made my touch gone in my Lenovo a2010
My case solved with touchscreen replacement as I supposed.
Related
Guys, I'm really in need of the superpowers of XDA community in this one, as I'm gonna lose my mind.
(PD: Not native english speaker here, pls be gentle )
Let's get into it:
I'm experienced in tweaking androids so I was just doing routine stuff in this one by unlocking bootloader, but it got bricked (still dont know why)
It astounds me the incredibly lack of documentation about this device in the entire interweb, given that is not soooo bad device actually, so the current situation is: device bricked, bootloop on huawei mediapad start logo and only access to fastboot mode (Volume down+Power).
1) Approach number 1: got the official firmware and tried to flash it by the official way, according to Huawei web,
httpxxx://consumer.huawei.com/en/tablets/support/manuals/s10-231l-en.htm
copied dload folder with update.app and stuff to the root of an 8GB fat-32'd MicroSD card hoping to get it installed but absolutely nothing happens. Volume UP+Volume Down+Power falls in bootloop again. No recovery no nothing apart fastboot mode.
2) Approach number 2: ADB drivers installed, combo ADB, Fastboot does NOT detect my device properly
Code:
C:\...\fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\...\fastboot>fastboot devices
? fastboot
Strange enough, it allows me to flash almost anything, so i flashed official boot, recovery and system images based on the official firmware:
Code:
C:\...\fastboot>fastboot flash boot boot.img
sending 'boot' (6708 KB)...
OKAY [ 0.260s]
writing 'boot'...
OKAY [ 0.917s]
finished. total time: 1.178s
C:\...\fastboot>fastboot flash recovery recovery.im
g
sending 'recovery' (9660 KB)...
OKAY [ 0.374s]
writing 'recovery'...
OKAY [ 1.332s]
finished. total time: 1.706s
C:\...\fastboot>fastboot flash system system.img
sending 'system' (738258 KB)...
OKAY [ 28.472s]
writing 'system'...
OKAY [ 43.332s]
finished. total time: 71.804
after reboot nothing happens, still in bootloop with no options to enter recovery mode, only fastboot working.
As said before, have browsed almost the entire interned but no luck by this time. Maybe i'm too focused on it.
Any XDA Gurú wants to get involved by giving advice? Will be greatly appreciated.
Anyone
Anyone?
Was hoping to find a solution here as like you I have searched the whole Internet and.... Nothing.
Exactly the same problem.
Would like to try flashing the official boot, but not sure how you did it, because Flash Tools needs a Scatterfile and Boot.img and the official boot is an Update.app
What program did you use?
Cheers,
Joe!
Still no solution for this? Got same problem.
Hi guys,
after flashing original recovery from Rashr, I have a hard bricked Meizu M1 Note. I can only boot into fastboot or VCOM (for SP Tool), no recovery, not normal boot.
Hope you can help me,
Thank you
Same story, even worse! I wanted to downgrade from LP to KK. I followed step by step guide posted in other forum. Everything works, but after 2 or 3 days, phone started to act very strange. Volume keys did not react properly (cant switch in recovery and made an screen shot for example), phone started to loose network coverage . I tried to reset it, but unfortunately no fastboot and recovery modes were present. The only way to switch in recovery was rashr tool. I decided to reflash recovery again and everything went wrong! The result was permanent restart, no recovery and fastboot modes. Maybe this method should be avoided. I know that everything I made is at my own risk, dont blame me.
Need advice to unbrick it. I was thinking to disassemble it and disconnect battery and try to resurrect it with adb?! The bad thing is that it wont turn into fastboot...pfuu.
Have some progress - phone can go into fastboot mode, but when I try to flash stock recovery, it reports error:
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (16384 KB)
OKAY [ 0.616s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017 because it is locked
)
finished. total time: 0.665s
Click to expand...
Click to collapse
Will appreciate any help. Thanks!
Any help?
Help
I have the same problem. Could anyone help us?
any help?
I have more or less the same problem but my cellular conects disconects preloader usb driver and don't see nothing in the screen, not logo, not recovery, not fastboot mode, any help?
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks
SOLVED
SOLVED
I've just flashed the current Le Max 2 TWRP package, but when I reboot into recovery mode the right half of the screen crashes, and the left half freezes.
The right half is covered in a multicoloured static, not dissimilar to when a ZIP cable isn't properly plugged in.
I'm unable to do anything at this point besides rebooting the phone.
I've tried flashing it again, to no avail.
Any suggestions? EUi is painful.
Okay, I've just tried it again and noticed that I missed the following in the cmd line.
C:\adb>fastboot flash resovery twrp-3.0.2-1-gemini.img
target reported max download size of 536870912 bytes
sending 'resovery' (57500 KB)...
OKAY [ 1.286s]
writing 'resovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.305s
I can't find anyone who's managed to solve this issue.
EDIT
Okay, saw my spelling mistake, fixed it and the issue persists - though I've noticed it is actually in the LeEco Recovery tool, not the TWRP one.
Okay, I've fixed it by using the most recent TWRP.
Hi there! My old Sony Xperia Tablet Z is running Resurrection ROM (Android 8), I use the tablet as a travelling companion. I also have TWRP as recovery.
Today I flashed the latest version of TWRP via the TWRP app, tried rebooting into it using a "quickboot" app (the tablet is rooted) but I ended up on a black screen. I can reset and Android runs no problem.
I then tried flashing TWRP via USB. I type
Code:
adb reboot bootloader
- it goes on a black screen and the status light is solid blue. I then run
Code:
fastboot flash recovery twrp.img
- the outcome is
Code:
sending 'recovery' (11796 KB)...
OKAY [ 0.379s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.384s
Then I tried
Code:
fastboot boot twrp.img
- and I get
Code:
downloading 'boot.img'...
OKAY [ 0.376s]
booting...
OKAY [ 0.032s]
finished. total time: 0.411s
but nothing happens.
Someone suggested to use
Code:
fastboot flash recovery_ramdisk twrp.img
instead (as I am on Oreo) but same error
I am stuck. Any help please? Thank you!
If bootloader is not working Use QPST Flash Tool to reflash everything back to stock.
Thanks. Too bad I don't have the original ROM backup anymore. I will try to download one, I hope all works well.
Can you just refresh me: when into "bootloader" I am supposed to see the bootloader menu on screen?
Edit: it seems that I am unable to install the Qualcomm drivers - Windows 10 reverts to generic drivers or ADB drivers. The drivers I downloaded don't seem to work with Windows 10?
any help on this please? Thank you!
Sorry for insisting - any help please? Can you point me to the right direction?
edit: I've done some homework and here is where I am.
Following some threads I tried flashing the stock ROM using flashtool. I used both the latest version and the "Emma" version from Sony.
I can connect to the tablet but I receive a the bundle does not match the connected device as - I reckon - the device is seen as an unknown device. The same with the Emma version, unknown device and as such, a No matching services as a reply.
Edit2: I found the solution for the above, I had to use the previous version of Flashtool. I flashed a stock ROM. Now it does not boot anymore. I have the SONY static logo and then a black screen. I tried again and also another version for my device but no luck.
Please help!
I am a bit lost here. Any help is appreciated. BTW, I can boot up the tablet perfectly fine and it works ok.
I'll just complete my very lonely thread for future references.
The issue was that I needed an older stock ROM as I was coming from Android 8 - a known issue apparently. I found a very old ROM (10.1 "store front"), that worked ok. From that one, I can do whatever I want. I ended up installing LineageOS which I find much faster than Resurrection.