Database Users

[Q] a2107 adb recovery?

I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..

Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"

Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers

da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351

I have the a2107-F will this root process work too?

valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.

I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.

[Q] galaxy s4 i9500

help! my phone is just restarting it self after it finishes booting, i can able to boot into download mode or recovery mode, but its failing to install a new ROM, i thought its was a soft brink. its acting like its protected in the way that i cant wipe or install anything through recovery or ordin. its saying failed.... even to wipe the system its failing to.. help

greatb4life said:
help! my phone is just restarting it self after it finishes booting, i can able to boot into download mode or recovery mode, but its failing to install a new ROM, i thought its was a soft brink. its acting like its protected in the way that i cant wipe or install anything through recovery or ordin. its saying failed.... even to wipe the system its failing to.. help
Click to expand...
Click to collapse
If you go to download mode and you can flash things via odin and it fails, it probably means that you have a defective usb port. Try another usb port and see if it solves the problem.

2722
Leonhan said:
If you go to download mode and you can flash things via odin and it fails, it probably means that you have a defective usb port. Try another usb port and see if it solves the problem.
Click to expand...
Click to collapse
have tried every port on my PC but still am getting the same response. i wonder why its even failing to delete the the installed os

greatb4life said:
help! my phone is just restarting it self after it finishes booting, i can able to boot into download mode or recovery mode, but its failing to install a new ROM, i thought its was a soft brink. its acting like its protected in the way that i cant wipe or install anything through recovery or ordin. its saying failed.... even to wipe the system its failing to.. help
Click to expand...
Click to collapse
Hi Mate,
If is restarting all the time it looks like is in contant reset , check you power button , maybe is stuck

system protected
Today it turn on for 5 minutes and I connected it to my pc to access it folder, i tried to delete some files and i got the message that android cannot be deleted the system is write protected. I removed it from the pc and tried to delete in its file manager the files where deleted but they came back and again it started restarting. I think that's the reason why its failing to install a new rom because of the protection. What else can i try?

Device not recognized/malfunctioned

Hello Guys! . I've got an issue on my hands, and I'm not really sure how can I solve it. I installed a new ROM, through TWRP recovery. After flashing, I tried to access the recovery, but the the phone started to bootloop, and sometimes it showed a greenish welcome screen. After a few bootloops, the phone started normally, entering the system. So, no recovery on it. Right now, after I tried to access the recovery a few times, the phone is blocked on bootloop . No access to files, no access to system, and no access to recovery also. Can you please advise what can I do furthermore?
Also, very important to mention is that the computer doesn;t seem to see the phone, I tried to another PC, the same thing. It says (in both computer cases) " USB device not recognised".
Is there any way to force somehow fastboot mode on the phone? ...
I really need some helping ideas, since I'm out....
Thank you!

Big problem with my htc U Ultra :(

Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.

SofianeLasri said:
Hello, I've a problem with my htc U Ultra (ocedugl). In fact, I upgraded supersu and when the phone was supposed to restart, I was stuck at the htc logo. I then had a backup of the boot and the system in reserve on my SD card, but when I wanted to restore them, I had the error 255. Only during the restoration of the system.
I do not know what to do, this phone is a real mystery to me. I have an internship tomorrow, not very practical suddenly. :/
The most problematic in all this is that twrp asks me for a password to decrypt the data at startup and I have the impression that I have only worsened the case. If anyone could help me quickly enough please.
PS: Me who I usually do alone, I must admit that I dry.
PS 2: I installed root switch for snapchat just before too, I do not know if that affects.
Click to expand...
Click to collapse
Try TWRP 3.2.1-1

minhnewpro said:
Try TWRP 3.2.1-1
Click to expand...
Click to collapse
Ho to install without an accessible system?

SofianeLasri said:
Ho to install without an accessible system?
Click to expand...
Click to collapse
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now

minhnewpro said:
Turn off your phone. Press Power and volume down at the same time to boot in to download mode. connect to PC and flash TWRP
Install via ADB
Open the folder where your TWRP Recovery .img file is saved.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
Once your device boots into download mode, type this into the command line.
fastboot flash recovery twrp-3.2.1-1.img
Once TWRP is successfully flashed on your device, you can use TWRP now
Click to expand...
Click to collapse
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.

SofianeLasri said:
thanks, i have now the twrp-3.2.1-1-oce but it still asks me for a password at startup and my restore still fails with error 255.
Click to expand...
Click to collapse
Maybe you need flash a new rom. Viper, Ledroid,...

minhnewpro said:
Maybe you need flash a new rom. Viper, Ledroid,...
Click to expand...
Click to collapse
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...

unmout data in internal storage and retore

SofianeLasri said:
Okay, I was saying that too. I try your custom rom then.
PS : Ah, I just saw that the post requests the latest version of the system, except that I do not have access ...
Click to expand...
Click to collapse
You can try flash rom without have same firmware. I'm using Oreo on Nougat firmware

Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD

SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
Oh it's good, it was really my card sd the problem.

SofianeLasri said:
Oh no, I just understand! My SD card seems locked in read only. I really have a bad day me! Between my hard drive doing anything and my phone ... xD
Click to expand...
Click to collapse
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash

minhnewpro said:
i don't know what extractly happened with your phone. You can access your storage by connect to PC when your phone in TWRP Recovery. Backup your personal data. Choose wipe => format data => type "yes" => copy Rom into your internal storage or SD Card and flash
Click to expand...
Click to collapse
No, in fact my sd card is dead. I can't write anymore on. I have save mys backup and restore my system. Thanks for the help!

HTC u ultra Oreo messed up my phone and now I need help.
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.

ibringthemadness said:
My story:
Bought a HTC U Ultra European.
I was kind of satisfied with it. The device didn't really live up to my expectations. But when it was upgraded to Oreo the screen start to flash when opening apps and Bluetooth sound went bad. It looks like the app opens twice. After a while it went even worse with the flashing.
Anyways I unlocked the bootloader and flashed TWRP 3.2. That process went fine then I wanted to flash leedroid to test something else (yes I saved a recovery file).
The result is now my device is working but I'm unable to flash twrp again. Since Oreo still sucks to u ultra and I want to downgrade to nougat since it works.
My adb (Linux) detects my device but when I start my HTC in download mode I'm unable to flash to since my PC says:
<waiting for device>
When I try to start it in recovery mode it sticks in a reboot loop.
And BTW I can't restore factory settings.
So if anyone can give me any answers it would be great.
Click to expand...
Click to collapse
Try reinstall driver, buy or borrow an other usb-c cable.

minhnewpro said:
Try reinstall driver, buy or borrow an other usb-c cable.
Click to expand...
Click to collapse
I already installed drivers and tried other cables. Did the procedure again bit with no results.
I think the big problem actually is that since the phone can't boot into recovery mode it get messed up.
I try to do a hard reset but every time I either get stuck in a bootloop or the phone boots into regular mode. So I literally can't do anything to fix this problem as far as I know.
Getting a little bit of frustrated over here.

Why you need reflash TWRP after used Leedroid's rom?

minhnewpro said:
Why you need reflash TWRP after used Leedroid's rom?
Click to expand...
Click to collapse
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.

ibringthemadness said:
Because I can't boot to recovery mode. Either I get stuck in a boot loop or the device boots just like I rebooted it. So I can't get to twrp and I can't flash anything. I can't hard reset either. All I can do is reboot, enter bootloader and enter download mode.
So I guess I'm stuck with Oreo that's a mess on my device.
Click to expand...
Click to collapse
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.

minhnewpro said:
Try boot into Download mode and Flash new TWRP https://dl.twrp.me/oce/twrp-3.2.2-0-oce.img.html
If your PC can not recognize your phone, try another PC.
Click to expand...
Click to collapse
Already tried to flash twrp-3.2.2...
Same result. None.
My PC finds my phone with no problem until I boot into download mode then it doesn't find it anymore.
Still another PC?

BIG PROBLEM! Moto C without solution! Throw it away? Or is there a Bad#@ there to help me?

I think I have an unsolved problem. I know it doesn't exist, but it's very hard to find it.
I know it's not the Plus, but the Model is the Moto C XT1754 (NAMATH) Android 7.0 Nogaut - NRD90M.060
And there is no specific topic for it, but they are very similar and I thought I could post it here.
It's a very complicated problem, so I'll explain in detail what happened and why I had to come here to solve it.
(translated)
- STARTING:
I installed a TWRP through the app, without unlocking the Bootloader.
Whenever I turned it on, at boot still, the message appeared:
'red state
Your device has failed verification and may not work properly
Your device will boot in 5 seconds'
But it called normally.
I installed 'Magisk Manager 24.2' by zip and app afterwards.
I activated 'Zygisk' and in DenyList I activated/hidden from Google Play Services completely. All.
I restarted the smartphone and Sitema started having numerous errors. Most of the apps that I opened, closed with error, and other apps in the background too, mainly Google Play Services.
I tried to solve this but I couldn't because the smartphone was unusable.
I decided to format by TWRP.
But when I tried to restart the device, I always entered TWRP and continued that message in Boot ('Red State Your Device...')
I decided to reinstall Stockrom from Moto C XT1754.
When I tried to install Stockrom through flash_tool, I couldn't.
It always gives error.
'BROM ERROR : S_BROM_CMD_STARTCMD_FAIL (0x7D5)
[BROM] Can not pass bootrom start command! Possibly target power up too early.
[HINT}:'
or this one is the most common:
'BROM ERROR : ?? (0x1)
[HINT];'
I even tried installing a Custom Rom via Sdcard , 'Viper-namath-20171206-Coral-v3.1.1-UNOFFICIAL' with the GAPPs, etc.
I can install the ROM. (but the GAPPS gives an error at the end of the installation) 'open_gapps-arm64-7.1-micro-20220215'
But I think this case is because it is not installing the Custom ROM correctly. (Because of the Locked Bootloader? Maybe... I'm kind of a layman on the subject)
Because when I restart the device after installation it goes back to TWRP.
I can't get into Fastboot mode with the command by the buttons on the device, only by TWRP when I access 'Reboot>Bootloader'.
Reboot and go to fastboot (Black screen, down there written '=> FASTBOOT mode...'
I've already tried to recover/rescue the device by Motorola/Lenovo's 'Rescue and Smart Assistant'. But when I try to rescue it (with it connected to TWRP) it asks to accept the message to enable USB debugging.
But I don't have access to this window through TWRP.
Here comes the big question, why I am not able to solve my problem:
I think my 'USB Debugging' was off/disabled before I erased everything (formatted).
I'll try Stockrom's Flash through TWRP to see if it solves the problem, but I don't think it will.
I think the problem may be with the 'USB Cable' as well. He's old. I tested with a non-original USB cable that I had to see and I can't either, the errors persisted.
I plan on getting another original to test as well.
Just an observation.
My device is being recognized as 'USB MTP Device' (under 'Portable Devices')
If anyone can save me, I'd really appreciate it!
Thanks in advance for all the help! Every opinion matters!

And when I give the command 'ADB Devices' my device appears 'unauthorized'
'ZW3223CGWK unauthorized'