Database Info

Need Help Changing / Accessing Recovery

I think I'm starting to understand this flashing recovery thing, but it doesn't seem to be working.
So I have downloaded the latest CWM and TWRP for my device (crespo?) and put the .img in a folder. I've tried both CWM and TWRP separately to no avail. I put the mac-related fastboot and adb files into the same folder. I open the terminal and flash the .img. I would like. It runs and says 'OKAY'.
Now, when I power down > hold volumne up + power > it brings me to the 'FASTBOOT MODE". It shows me my lock state is unlocked and gives me the option to:
REBOOT BOOTLOADER
REBOOT
RECOVERY
POWER OFF
So I select RECOVERY and this is where it gets weird..
Reboots and brings me to a screen with the android guy lying down and a red caution triangle coming out of his chest. If I leave it, it will eventually reboot normally. If I hold the power and volume up button again for an extended duration (or some combination of buttons, i usually just hold random combinations until something pops up), then i get the 'android ssytem recovery <3e> screen. It looks like a minimal CWM recovery screen with Reboot system now, apply update from ADB, apply update from /sdcard, wipe data/factory reset, and wipe cache partition.
This doesn't seem like the CWM or TWRP that I flashed. It also won't let me flash a ROM when I select 'apply update from /sdcard'.
I'm pretty sure I'm not installing CWM properly.. but when I run the terminal (command prompt) it seems to run fine.
Does anyone have any suggestions?

SOLVED:
So I messed around and solved my problem. Apparently entering CWM recovery on the Nexus S is more challenging than it should be.
For those of you with the same problem, here is the solution:
Enter fastboot mode > connect your device > open your command prompt (terminal)
I would flash CWM to your phone first fastboot flash recovery <recovery.img>. When it finishes and tells you everything is okay, type:
fastboot boot <recovery.img>.
This will boot your phone into CWM recovery!

[Q] HELP needed for root my 1+1

ok guyz
I have this phone (with CM11S updated) since a month and finally, only from yesterday, I managed to get access to the fastboot command.
Via windows 7-64 there was no way do do this.
I've installed a windows 8 virtual machine and it works fine.
Installed adb+fastboot
downloaded bacon image (renamed twrp.img)
installed universal naked drivers
downloaded supersu zip
I followed the classic procedure to root the phone and
http:
//s29.postimg.org/nwypa3lfr/Catturaz.png
as per the screenshot, the result seams to be "OKAY", but when I reboot on recovery, I have already the original and unrooted "simple recovery"; then I cannot install supersu
why the hell !!!

Settings > About phone > Tap on Build number 7 times to enable Developer options.
Then go back to Settings > Developer options > disable Update recovery with system updates

Holy Cow!!!1!!
I think i've solved
I think just have solved, by a simple trick:
No needed to flash the recovery; simply when in fastboot, do not flash the recovery but reboot loading the new (and temporary) recovery. Whit this simple trick you are able to install the supersu.
then summing up:
enter on the command line adb reboot bootloader
(wait for a second and on the phone screen appears ###fastboot...)
enter on the command line fastboot boot twrp.img
(wait 5 to 10 seconds and appears the teamwin bacon recovery)
press install and load the supersu zip previously loaded on the phone
reboot
enter on the supersu app and DEselect "Respect CM’s root Policy"
et voilà
Of course the teamwin recovery is NOT installed on the phone and you already have the OLD simple recovery , but the phone is rooted and YOU HAVE THE POWEEEER!!!1!

luasso said:
Holy Cow!!!1!!
I think i've solved
I think just have solved, by a simple trick:
No needed to flash the recovery; simply when in fastboot, do not flash the recovery but reboot loading the new (and temporary) recovery. Whit this simple trick you are able to install the supersu.
then summing up:
enter on the command line adb reboot bootloader
(wait for a second and on the phone screen appears ###fastboot...)
enter on the command line fastboot boot twrp.img
(wait 5 to 10 seconds and appears the teamwin bacon recovery)
press install and load the supersu zip previously loaded on the phone
reboot
enter on the supersu app and DEselect "Respect CM’s root Policy"
et voilà
Of course the teamwin recovery is NOT installed on the phone and you already have the OLD simple recovery , but the phone is rooted and YOU HAVE THE POWEEEER!!!1!
Click to expand...
Click to collapse
that won't keep the custom recovery forever though mate. you need to fastboot flash recovery recovery.img
Artem said in another thread that you have to go into developer settings and uncheck the update recovery one. then you can flash the recovery and it will stick permanently.
BTW: it works on windows 7 64bit for me. i have the full sdk installed though.

MontAlbert said:
that won't keep the custom recovery forever though mate. you need to fastboot flash recovery recovery.img
Artem said in another thread that you have to go into developer settings and uncheck the update recovery one. then you can flash the recovery and it will stick permanently.
BTW: it works on windows 7 64bit for me. i have the full sdk installed though.
Click to expand...
Click to collapse
That's an option I unchecked before doing everything. That's why I have not replied to Chromium.
And i've tried also with the SDK complete installed on Win7.64.
It doesn't work for me; I dont know why (yet), but by now with this workaround i'm satisfied.
By the way, the OnePlus One is a very goooood phone

[6039K] "reboot recovery" command not working

I have the Idol 3 6039K (Dual SIM) model with latest firmware, Rooted and with TWRP Recovery 2.8.7.0 flashed on the phone.
Everything is working fine, only I have noticed that "Reboot to Recovery" via a software command is not working. Instead of rebooting into recovery my phone does a normal system reboot. Not a big issue but I wonder if others have the same problem.
Details:
- Phone: Idol 3 model 6039K with latest firmware 5.0.2 build 01006
- Fastboot commands restored following instructions in this thread and rooted by booting the TWRP recovery image using fastboot and installing UPDATE-SuperSU-v2.46.zip file using TWRP.
Following commands are working from android terminal after entering "su" or from windows command prompt using adb:
- "reboot" => Phone reboots system as expected => OK
- "reboot bootloader" => Phone reboots in bootloader => OK.
- When phone has booted into bootloader the fastboot commands are working as expected => OK.
Booting into TWRP Recovery is working by turning OFF the phone and pressing Volume UP + Power buttons at the same time.
Reboot to Recovery from inside TWRP is also working.
Only the following is not working from android terminal or from windows using adb:
- "reboot recovery" => Phone does not reboot in TWRP Recovery but does a normal system reboot as if only "reboot" is entered.
- Also Reboot to Recovery using applications like Titanium Backup or Quick Boot app results in a normal system reboot instead of reboot to recovery.
Questions that I have:
- Can somebody let me know if the "reboot recovery" command is working on his/her phone?
- Has anybody an idea what could be the reason that reboot to recovery is not working on my phone? Could it be related to the firmware version that I use or could there be another cause?
Thanks in advance for any feedback or ideas.

Maybe my opening post was too long?
Could somebody with a rooted Idol 3 phone tell me what happens after typing the following 2 commands in a command line shell:
su
reboot recovery
The phone should reboot into recovery mode, but my phone does a normal reboot.

Hey Ho...
My Idol 3 also boots up in system by "fastboot recovery".
To go into recovery with stock firmware , rootet, i used the "ndr utils" from Playstore.
Now i´m on CM12.1 .... and have the "recovery boot" option in pomermenu

neutrinobox said:
My Idol 3 also boots up in system by "fastboot recovery".
To go into recovery with stock firmware , rootet, i used the "ndr utils" from Playstore.
Now i´m on CM12.1 .... and have the "recovery boot" option in pomermenu
Click to expand...
Click to collapse
Thanks for your reply. Btw, as far as I can see "fastboot recovery" is not a valid command.
Command "adb reboot recovery" from windows command prompt works for 2 other Android devices that I have (Samsung Galaxy Gio and Asus TF303K tablet both reboot in recovery mode), but my Idol 3 6039K reboots in system.
Some more experiments that I did:
- Went back to the original Stock firmware 5.0.2 build 01006 including stock recovery => reboot recovery command results in reboot in system
- Installed NDRutils from Playstore and selected "Reboot to Primary Recovery" => reboot recovery command results in reboot in system
I suspect that Android apps simply make use of the /system/bin/reboot binary that is included in the stock firmware. If this binary does not support reboot in recovery mode, Android apps can also not initialize a reboot to recovery mode. It looks to me that "reboot recovery" is simply not supported by the reboot binary that comes with the stock firmware. Maybe it has worked with earlier firmware, but the reboot binary that comes with the latest firmware does not seem to support it.
Is there anybody out there with an Idol 3 phone for who "reboot recovery" is working? If so, please let us know!

Hello CornelisJ,
which file did you use to restore the fastboot commands? The 6039S?
Gesendet von meinem 6039K mit Hilfe von XDA Forums

Maulschelle said:
Hello CornelisJ,
which file did you use to restore the fastboot commands? The 6039S?
Click to expand...
Click to collapse
Indeed for restoring the fastboot commands on my 6039K with firmware 5.0.2 build 01006 I have used the files for the 6039S.
(see opening post of this thread for the download link).

TWRP 3.1.0-0 for V3961 (Cloudfone Excite Prime 2, Wiko U Pulse, Qmobile CS1 Plus)

(Can't put the [RECOVERY][PORT] in title because it exceeds character limit)
Bugs:
- MTP (or just my driver?)
- The rest is just working fine (including adb)
How to boot?
Due to how this device works, we can only flash a stock recovery or else it won't boot with custom recovery at all
Click to expand...
Click to collapse
Download TWRP here: https://androidfilehost.com/?fid=818070582850505557
& (skip if already installed) install adb & fastboot drivers here: https://forum.xda-developers.com/showthread.php?t=2588979
1. Enable OEM unlocking & USB debugging via Settings > Developer Options
2. Open Command Prompt & "cd" where you downloaded the image & type:
Code:
adb reboot bootloader
Allow it when a prompt shows up then try again if it doesn't work
Code:
fastboot oem unlock
SKIP THIS STEP WHEN ALREADY UNLOCKED!
When a warning about unlocking bootloader shows up, press volume up (will factory reset your device after rebooting)
Code:
fastboot boot TWRP-3.1.0-0_v3961.img
There! Enjoy TWRP & READ NOTES!
NOTES:
- If this is the first time you booted TWRP, install SuperSU zip (or use "adb reboot") or else the device won't boot to Android after rebooting using TWRP's reboot option! (modifies /system partition, renames recovery-from-boot.p to recovery-from-boot.bak, causing dm-verity to invalidate system partition)
- If your /data partition is throwing errors, you need to reboot it using "adb reboot", since you've just unlocked the bootloader & needs to be formatted via stock recovery
- Since it's just "fastboot boot", it won't stay on your device (don't even try to "fastboot flash" it)

Help me Please
Pls help. My Cloudfone Excite Prime 2 got bootlopp in orange state after trying to fastboot unlock oem and flashed twrp. is there any fix please. I cant turn off my phone its always restarting on orange state on repeat.

Bootloop (
My wiko u pluse got bootloop too :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

Fixed - Forgot to read note LOL
I fastboot flash it lol :v

Hello,
Does it work on U-pulse lite ?
Thanks
Laurent

link for download twrp not working
pls provide link for download twrp u pulse v3961, that one not working anymore

twrp?
pls provide twrp for u pulse v3961, thanks

Update the twrp link please, i need it for my wiko u pulse

3DMapPlayer said:
(Can't put the [RECOVERY][PORT] in title because it exceeds character limit)
Bugs:
- MTP (or just my driver?)
- The rest is just working fine (including adb)
How to boot?
Download TWRP here: https://androidfilehost.com/?fid=818070582850505557
& (skip if already installed) install adb & fastboot drivers here: https://forum.xda-developers.com/showthread.php?t=2588979
1. Enable OEM unlocking & USB debugging via Settings > Developer Options
2. Open Command Prompt & "cd" where you downloaded the image & type:
Code:
adb reboot bootloader
Allow it when a prompt shows up then try again if it doesn't work
Code:
fastboot oem unlock
SKIP THIS STEP WHEN ALREADY UNLOCKED!
When a warning about unlocking bootloader shows up, press volume up (will factory reset your device after rebooting)
Code:
fastboot boot TWRP-3.1.0-0_v3961.img
There! Enjoy TWRP & READ NOTES!
NOTES:
- If this is the first time you booted TWRP, install SuperSU zip (or use "adb reboot") or else the device won't boot to Android after rebooting using TWRP's reboot option! (modifies /system partition, renames recovery-from-boot.p to recovery-from-boot.bak, causing dm-verity to invalidate system partition)
- If your /data partition is throwing errors, you need to reboot it using "adb reboot", since you've just unlocked the bootloader & needs to be formatted via stock recovery
- Since it's just "fastboot boot", it won't stay on your device (don't even try to "fastboot flash" it)
Click to expand...
Click to collapse

I have old phone here which is Cloudfone next lite. I want to root this phone, but I need twrp first but I don't see twrp for my phone. Is there somebody can help me 🥹

Lenovo TB-X605F twrp?

I was able to get the device rooted with the magisk boot image patch method, but I was seeing if I can get twrp?

turboperson123 said:
I was able to get the device rooted with the magisk boot image patch method, but I was seeing if I can get twrp?
Click to expand...
Click to collapse
Could you link me to the method you used for root please?
Sent from my God Mode 8

Hi
I'm highly interested too. Could you share the method please?
Do you manage to install twrp?
Thanks!

Hello,
How do you do to unlock bootloader.I was able to download and patch with magisk the last ROM but I can't flash it !
Please would you tell us how you do that ?
Thanks

here is the link https://forum.xda-developers.com/ge...agisk-root-t3992477/post80692227#post80692227

Thank you !

go to settings and enable developer options, then go to developer options / enable usb debugging and enable oem unlock
then on pc if you have adb and fastboot installed then type adb reboot bootloader
then once the tablet is in fastboot type fastboot oem unlock-go to unlock the bootloader

TWRP 3.3.1-0 TB-X605F Lenovo Smart Tab M10
i used the twrp port from stock recovery method here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
"warning this will wipe data, bootloader needs to be unlocked, computer has adb and fastboot installed"
1. download twrp from here http://www.mediafire.com/file/tn7csi4gzm91w7v/twrp-3.3.1-0-X605F.img/file
2. then on the tablet go to settings / Developer mode / usb debugging
3. connect the tablet to pc with usb cable then on the tablet you will see usb debugging authorizations, click on allow always to make the device debuggable
4. on pc launch command prompt then type "adb reboot bootloader" to reboot into bootloader
5. once in bootloader type "fastboot flash recovery "the directory of the twrp-recovery.img" once flashed then type "fastboot reboot"
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here http://www.mediafire.com/file/ndhe4ewlzlffdur/Disable-dm-verity-forceencryption.zip/file then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.

Working fine from my side

Turbo, many Thanks!
It works perfectly ! ?

turboperson123 said:
i used the twrp port from stock recovery method here https://forum.xda-developers.com/android/general/guide-porting-twrp-source-t3843473
"warning this will wipe data, bootloader needs to be unlocked, computer has adb and fastboot installed"
1. download twrp from here http://www.mediafire.com/file/tn7csi4gzm91w7v/twrp-3.3.1-0-X605F.img/file
2. then on the tablet go to settings / Developer mode / usb debugging
3. connect the tablet to pc with usb cable then on the tablet you will see usb debugging authorizations, click on allow always to make the device debuggable
4. on pc launch command prompt then type "adb reboot bootloader" to reboot into bootloader
5. once in bootloader type "fastboot flash recovery "the directory of the twrp-recovery.img" once flashed then type "fastboot reboot"
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here http://www.mediafire.com/file/ndhe4ewlzlffdur/Disable-dm-verity-forceencryption.zip/file then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Click to expand...
Click to collapse
Good job, @turboperson123 ! @Monpseud0 pointed me over here.
I've got some time this week & I'm going to start on a version that will handle encryption. You can find the device tree and code here. I've included a link to this thread.

I bricked my device. Rebooting the system from TWRP only gets me back into TWRP.
Am afraid I will have to flash a new rom.
Does anyone know where to download a working rom for TB-X065F
Help much appreciated.

stefankkl said:
I bricked my device. Rebooting the system from TWRP only gets me back into TWRP.
Am afraid I will have to flash a new rom.
Does anyone know where to download a working rom for TB-X065F
Help much appreciated.
Click to expand...
Click to collapse
Easiest thing to do is use LMSA. It's available on Lenovo's support page: https://pcsupport.lenovo.com/au/en/...r-list/component?name=Software and Utilities.

Still unable to re-flash stock ROM
Yahoo Mike said:
Easiest thing to do is use LMSA. It's available on Lenovo's support page:
Click to expand...
Click to collapse
I can download the ROM through LMSA, but not flash it.
Trying to do so yields a "complete" message from LMSA after only a few seconds, but then rebooting the device only gets me back into TWRP.
I also tried to flash all system_xx.img from the ROM using fastboot flash system system_xx.img ,
and to flash all vendor_xx.img from the ROM using fastboot flash vendor vendor_xx.img.
Fastboot performs this operation, but then rebooting gets me back into TWRP again.
Trying to reboot the system from TWRP yields the message "no system installed"
Help much appreciated.

stefankkl said:
I can download the ROM through LMSA, but not flash it.
Trying to do so yields a "complete" message from LMSA after only a few seconds, but then rebooting the device only gets me back into TWRP.
I also tried to flash all system_xx.img from the ROM using fastboot flash system system_xx.img ,
and to flash all vendor_xx.img from the ROM using fastboot flash vendor vendor_xx.img.
Fastboot performs this operation, but then rebooting gets me back into TWRP again.
Trying to reboot the system from TWRP yields the message "no system installed"
Help much appreciated.
Click to expand...
Click to collapse
Tough one! Try this. It will wipe your data partition, though.
If it will let you, power down the tablet for about 10mins. Then boot into TWRP. Go to "Wipe" and swipe for Data/Factory Reset. Reboot.
If the M10 still won't boot, in TWRP re-format Data (by typing 'yes' under Wipe->Format Data), and wipe cache and Dalvik Cache. I think dalvik is under Wipe->Advanced. Factory reset again. Reboot.
As an absolute last resort, you might try fixing permissions in TWRP under "Advanced". But I don't think that's going to do much, because you haven't booted the ROM successfully yet.
Hope one of these works for you. Let us know what worked for you. If nothing works, PM me and we'll try some other things.

Lenovo Logo THEN black screen -- DEAD
turboperson123 said:
6. once tablet rebooted type "adb reboot recovery" on pc to reboot into recovery, warning you will see /data mounting errors to fix this on the tablet go to wipe / format data and type yes to format data, then go back to main screen then go to reboot / recovery to reboot back into recovery.
7. on pc download dm-verity-forceencryption zip file here then on the tablet go to advanced / adb sideload then swipe it, then on pc type "adb sideload the directory where you put the zip file" once flashed then go to the main screen then go to reboot / system to reboot system
then it should boot up.
Click to expand...
Click to collapse
I followed the instructions but on the last step of rebooting to system the device restarts, shows the Lenovo logo then it goes to a black / blanks screen. It appears to have shut down. I must hold the power button for several seconds before it wakes up (or restarts?) and does this all over again -- shows the Lenovo logo then black screen.
For the record the device was already rooted with Magisk. I was just trying to do a TWRP backup but found /data mounting errors so tried following steps 6 & 7. At the moment the device refuses to boot up. I am unable to get back into Recovery Mode. The ONLY thing i can do is get into FASTBOOT mode and issue commands from CLI.
The following hardware key combos produce the same results -- tablet turns on to show the Lenovo logo, after a few seconds the screen goes black (the device appears to have turned off):
x Power key
x Power Key + Volume Down
x Power Key + Volume Up
x Power Key + Volume Up + Volume Down
** Release of keys is done once Lenovo logo appears
Any ideas?
UPDATE
I went ahead and performed: fastboot flash boot boot.img << the boot.img was the earlier patched magisk image i used to get the rooted working tablet.
After performing the above the tablet turned on and is now showing the Lenovo logo however it does nothing else --- it remains on the logo forever. I am able to get into TWRP recovery. I went ahead and wiped Dalvik, Cache, and Data. Rebooted to System but still it is stuck on the Lenovo Logo.
The device if fully charged.

crosis99 said:
I followed the instructions but on the last step of rebooting to system the device restarts, shows the Lenovo logo then it goes to a black / blanks screen. It appears to have shut down. I must hold the power button for several seconds before it wakes up (or restarts?) and does this all over again -- shows the Lenovo logo then black screen.
Any ideas?
Click to expand...
Click to collapse
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.
Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.

Yahoo Mike said:
You could try recovering the tablet with LMSA. See this post. You'll lose all your existing data and setup on the tablet, though.
Not sure what went wrong for you. Do you have a TB-X605F with Snapdragon 450 SOC? The existing TWRP is only for the SDA450. I'm working on one for the M10s with SDA429.
Click to expand...
Click to collapse
Thanks for the response. Yes mine has the Snapdragon 450. I will investigate the LMSA. Been messing around all day but made no progress -- not even QPST is working out.