Database Info

[Q] need help flashing CWM on the latest 1.63.531.2 710RD mt4gs

and i went on this link below
[How To] Flash ICS ROMs with S-ON Unlocked
I'm assuming you have
•Fastboot set up as a PATH, or copied to the folder you are extracting boot.img to
•HTC Drivers installed
•Clockwork Recovery
i have the drivers installed but i dont know the path and its not giving me details and to make it easyier to me i put everything on my desktop so please help me out here cause im about to sell this device and buy myself a g2 or g2x or a samsung android phone i really like bulletproof rom installed bad all i need for help is get CWM on this phone then i can handle it from there thanks.

you can download rom manager from play and install cwm

{
"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"
}

You at least have to be unlocked and rooted. You're obviously not rooted, yet.

see
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me

crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement

crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Just being unlocked is not the same as being rooted. You need to be Unlocked AND rooted to install CWM through Root Manager. You're only half of that.

Coug76 said:
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
nope im having trouble doing that i need help on that part

With an unlocked bootloader I simply copy the fastboot and adb files, as well as whatever recovery image I want to flash and push the recovery via fastboot... however if you aren't confident in your skills with the command prompt or fastboot there is always the all-in-one toolkit for the MT4GS that can be downloaded from its own thread in the dev forums (I don't have the link handy but it seemed to work for me on my sister's mt4gs).

I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted. I am also unable to install anything like Busybox or ROM Toolbox. It seems like the root just wasn't properly set up but none of the methods I've found actually work. I have tried to redo the rooting process, but to no avail.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.

I'd say do a flash of CWM via adb. Then install Superuser through CWM using a zipped Superuser. Worked flawlessly for me.

yupThisIsMyName said:
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
Click to expand...
Click to collapse
Are you using the trackpad to select things in recovery? All of my other phones used power while in recovery to select things but the doubleshot uses trackpad to select
Sent from my myTouch_4G_Slide using Tapatalk 2

I'm of two different schools of thought here - my first thought is bad download of CWM... Honestly I'd just read up on fastboot flashing the recovery image and do that to ensure a good root. However as noted above the trackpad select did throw me off at first.
Sent from my myTouch_4G_Slide using XDA

OK, it looks like I don't actually have S-Off and I've got the newer Hboot which, from what I can tell, prevents me from using this method and the only two ways to do this seem to involve either doing some crazy stuff with wires or flashing stuff without taking a backup first. Both of these methods make me very nervous, especially since as far as I can tell there is no way to use anything like Odin or RSD Lite with this phone to restore it in case something gets messed up.
If anyone has a way I can take a backup before flashing a ROM or, better yet, has a way to restore the phone completely in case something goes awry that would be awesome.

Update: Yeah, looks like it was the trackpad thing preventing me from doing this properly. Totally bizarre considering the fact that I was able to select things just fine using the volume buttons but when I hit power (which selects on most devices), it didn't work right.
Thanks for helping me get past this hurdle everyone! Hopefully I can figure out how to get s-off.
Edit: Update - I flashed a ROM that already had root and now that works too. Good enough for now, I'll wait for a less scarey method to get S-off. I'm not about to start messing around with wires.

[Q] HTC ONE S booting into recovery then into the rom

this is happening since i rooted my htc with the supersu zip method .
so here is the problem:
when the htc's battery dies and i connect it to the wall charger or usb so it boots into recovery and then when i press reboot system now it reboots normally. (running clockworkmod touch recovery)
how do i make it boot straight into the rom without booting into recovery?

Install TWRP- 2.3.0.0 , and stay away wrom clockwork. And install custom rom, they all are properly rooted, and busybox installed.

Still have the problem

Your phone isn't properly rooted, as this zip method fails some time.
Simply grab Su_Bbox* from here and flash it in recovery. If CWM recovery fails to flash that, download TWRP recovery from the same linked folder and 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' in fastboot mode of your phone.
SU and Busybox need to be properly installed for working root. It's not only (any) SU making it!

rootrider said:
Your phone isn't properly rooted, as this zip method fails some time.
Simply grab Su_Bbox* from here and flash it in recovery. If CWM recovery fails to flash that, download TWRP recovery from the same linked folder and 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' in fastboot mode of your phone.
SU and Busybox need to be properly installed for working root. It's not only (any) SU making it!
Click to expand...
Click to collapse
i saw you have a file called ville recovery signed is it the stock recovery?

LSGio said:
i saw you have a file called ville recovery signed is it the stock recovery?
Click to expand...
Click to collapse
Yes!

rootrider said:
Yes!
Click to expand...
Click to collapse
is it compatible with the s4 or s3 htc one s?

S4
--- edit ---
Whatever device you have, SU_Bbox will work on any phone, as it is device unindependant!!!

rootrider said:
S4
Click to expand...
Click to collapse
now im flashing the bbox file and gonna see how it goes
didn't fix my problem
did this happened to you and then after flashing bbox its gone?

LSGio said:
did this happened to you and then after flashing bbox its gone?
Click to expand...
Click to collapse
I had that reboot into recovery problem some time ago... But I'm not shure about the solution now...
Well, I'd need to know a few things now.
Device? S3 S4?
Rom? Stock or custom, if custom, which rom?
Recovery? TWRP or CWM and which version?
Kernel? Custom or stock?
Bootloader version and CID?

rootrider said:
I had that reboot into recovery problem some time ago... But I'm not shure about the solution now...
Well, I'd need to know a few things now.
Device? S3 S4?
Rom? Stock or custom, if custom, which rom?
Recovery? TWRP or CWM and which version?
Kernel? Custom or stock?
Bootloader version and CID?
Click to expand...
Click to collapse
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery

LSGio said:
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
Click to expand...
Click to collapse
if you have skype it would be easier mine is:
lior_shvartz2

LSGio said:
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
Click to expand...
Click to collapse
Ok, stock JB would mean that there is a write protection, invented with HTCs JB update (as long as you're using the stock kernel...).
To solve this, you'd need to flash any sense custom kernel (bricked, bulletproof, ElementalX). I'd recommend bulletproof (close to stock so).
BL and CID can be checked by starting bootloader mode. You'll see it below the tampered flag.
As Fanagoreca already mentioned, you should flash TWRP recovery (the one from my link above is 2.3.3.0, working good and for S4) by booting into fastboot mode and entering 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from terminal/command window.
After that you should flash a custom kernel to remove write protection, either in recovery or fastboot mode ('fastboot flash boot boot.img'). But through recovery should work.
Then flash SU_Bbox again from TWRP. The point is, I don't know if your version of CWM works as it should. Since the time this phone came out, CWM always had bugs and wasn't working in some ways. TWRP was pretty good to go with up to 2.3.3.0, after that version it started to become buggy for some things.
So just give it a try. I think it's not a big problem.
--- edit ---
Sorry, don't have skype.
---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------
...
BL version comes into game, if you're s-on. Versions > 1.09 make it necessary to flash the kernel separately from your rom in fastboot mode. Else your system won't start, as there is no kernel...
Usually you'd unzip the kernel (aka boot.img) from your rom.zip and flash it with: 'fastboot flash boot boot.img' in fastboot mode.
CID will be relevant for receiving OTA updates or gaining s-off. So it's not that important this time.

rootrider said:
Ok, stock JB would mean that there is a write protection, invented with HTCs JB update (as long as you're using the stock kernel...).
To solve this, you'd need to flash any sense custom kernel (bricked, bulletproof, ElementalX). I'd recommend bulletproof (close to stock so).
BL and CID can be checked by starting bootloader mode. You'll see it below the tampered flag.
As Fanagoreca already mentioned, you should flash TWRP recovery (the one from my link above is 2.3.3.0, working good and for S4) by booting into fastboot mode and entering 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from terminal/command window.
After that you should flash a custom kernel to remove write protection, either in recovery or fastboot mode ('fastboot flash boot boot.img'). But through recovery should work.
Then flash SU_Bbox again from TWRP. The point is, I don't know if your version of CWM works as it should. Since the time this phone came out, CWM always had bugs and wasn't working in some ways. TWRP was pretty good to go with up to 2.3.3.0, after that version it started to become buggy for some things.
So just give it a try. I think it's not a big problem.
--- edit ---
Sorry, don't have skype.
---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------
...
BL version comes into game, if you're s-on. Versions > 1.09 make it necessary to flash the kernel separately from your rom in fastboot mode. Else your system won't start, as there is no kernel...
Usually you'd unzip the kernel (aka boot.img) from your rom.zip and flash it with: 'fastboot flash boot boot.img' in fastboot mode.
CID will be relevant for receiving OTA updates or gaining s-off. So it's not that important this time.
Click to expand...
Click to collapse
im using ics right now (4.0.3) so i want to unroot and relock BL to update but firsst i want so solve this problem.
if i'll update will it fix my problem?
one more question:
the bootloader version is the HBOOT version? if it does so mine is 1.13

LSGio said:
im using ics right now (4.0.3) so i want to unroot and relock BL to update but firsst i want so solve this problem.
if i'll update will it fix my problem?
one more question:
the bootloader version is the HBOOT version? if it does so mine is 1.13
Click to expand...
Click to collapse
The update won't fix your problem. I think it's recovery related. So changing the recovery might solve it. You still should try that first. For running RUUs or OTA update you will need to flash custom recovery and relock bootloader. The tampered flag can only be removed when you s-off your device.
HBOOT version is bootloader version, here 1.13.
Which country you are living in? Be warned, that when you flash the latest OTA update (JB) from TMO US your partition for writing CID will be locked. And if you can't superCID your phone anymore, you will not be able to get s-off!
You should consider superCID'ing and getting s-off first. Once being s-off you can do anything with your phone.

rootrider said:
The update won't fix your problem. I think it's recovery related. So changing the recovery might solve it. You still should try that first. For running RUUs or OTA update you will need to flash custom recovery and relock bootloader. The tampered flag can only be removed when you s-off your device.
HBOOT version is bootloader version, here 1.13.
Which country you are living in? Be warned, that when you flash the latest OTA update (JB) from TMO US your partition for writing CID will be locked. And if you can't superCID your phone anymore, you will not be able to get s-off!
You should consider superCID'ing and getting s-off first. Once being s-off you can do anything with your phone.
Click to expand...
Click to collapse
i fixed my problem by updating trough OTA to JB (im from israel)
and btw you said that i should install custom recovery and relock to update but it failed so i flashed the stock recovery and than relocked and i achieved success.
do you have an idea when sense 5 is coming out to our device ?

LSGio said:
i fixed my problem by updating trough OTA to JB (im from israel)
and btw you said that i should install custom recovery and relock to update but it failed so i flashed the stock recovery and than relocked and i achieved success.
Click to expand...
Click to collapse
oops, sorry, you're right. I meant stock recovery but wrote custom.
LSGio said:
do you have an idea when sense 5 is coming out to our device ?
Click to expand...
Click to collapse
The first thing going on will be 4.2.2 and sense 5 for the m7 (one) in may or june. The One X will get updated to that as well around one month later, including blinkfeed and zoe. The One S will also be updated to Sense 5 but if there will be blinkfeed and zoe might be doubted. I personally think that this will be 4.2.2 as well.
I can't find the sources for that anymore, but I was reading about that yesterday or the day before.

rootrider said:
oops, sorry, you're right. I meant stock recovery but wrote custom.
The first thing going on will be 4.2.2 and sense 5 for the m7 (one) in may or june. The One X will get updated to that as well around one month later, including blinkfeed and zoe. The One S will also be updated to Sense 5 but if there will be blinkfeed and zoe might be doubted. I personally think that this will be 4.2.2 as well.
I can't find the sources for that anymore, but I was reading about that yesterday or the day before.
Click to expand...
Click to collapse
ok thank you for all this info now what is the proccess to S-OFF'ing my device
these are my device's stats:
{
"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"
}
And Hboot version is 2.15
CPU: S4
And i'm also using the latest hasoon2000's toolkit which looks like this:

UP!!

Go Here for instructions to S-Off

[Q] Flash Stock and Unroot without USB possible? [SOLVED]

Hello Nexus friends!
Hope someone can help me:
Is there a way to flash my nexus 5 back to stock and unroot without USB?
I think my USB port is dead, it doesnt load and I m not able to connect it with any computer. I wiped it but nothing changed.
History:
I flashed and rooted my phone with Nexus Root Toolkit from stock (4.4.2 (KOT49H) i think) now after OTA updates its runnig 4.4.4 (KTU84P).
plz help!
regards
Mike

You could flash a stock recovery flashable ROM....would need root for that obviously.
As far as flashing stock recovery....not sure about that one. Maybe flashify can help? Never used it myself. You need a flashable stock recovery tho.
Also, the boot loader will be unlocked still, so that's kind of a dead giveaway. Nothing you can do about that without connecting to a computer for fastboot.

Need to know the full situation.
If you've lost root you NEED a custom recovery. If you have stock recovery, you NEED root.
OTA removes root and custom recovery.
Please give situation report.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Need to know the full situation.
If you've lost root you NEED a custom recovery. If you have stock recovery, you NEED root.
OTA removes root and custom recovery.
Please give situation report.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
OTA removes ROOT? Didnt know that...
{
"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"
}
So now my Phone is unrooted and stock? SuperSU says its not installed but i have the app icon...?

Ok so you're stock unrooted. What recovery have you got?
Sent from my Nexus 5 using Tapatalk

rootSU said:
Ok so you're stock unrooted. What recovery have you got?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is there a way to read the header of the .ab files?
01-17-2014_13-37.ab (should be Stock 4.4.2 (KOT49H))
But I dont think its unrooted
I want back to stock ROM, RECOVERY, BOOTLOADER... to send it back for warranty repair of the USB port!
Thank you for your efforts!

w1m9 said:
Is there a way to read the header of the .ab files?
01-17-2014_13-37.ab (should be Stock 4.4.2 (KOT49H))
But I dont think its unrooted View attachment 2857791
I want back to stock ROM, RECOVERY, BOOTLOADER... to send it back for warranty repair of the USB port!
Thank you for your efforts!
Click to expand...
Click to collapse
I can walk you through it but I need to know for definite your current situation.
I need you to have either root, or a custom recovery.
To check custom recovery, hold vol down + power to boot to bootloader. Then use Volume up / down to navigate to "recovery" and press power to select. I want to see the recovery screen. Usually OTA will remove root and custom recovery.
Also, use root checker to check if you have root - I expect you will not have it.
First install SuperSU
https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Then install root checker
https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck

rootSU said:
I can walk you through it but I need to know for definite your current situation.
I need you to have either root, or a custom recovery.
To check custom recovery, hold vol down + power to boot to bootloader. Then use Volume up / down to navigate to "recovery" and press power to select. I want to see the recovery screen. Usually OTA will remove root and custom recovery.
Also, use root checker to check if you have root - I expect you will not have it.
First install SuperSU
Then install root checker
Click to expand...
Click to collapse
OK u r right!! It is not rooted... here my recovery

w1m9 said:
OK u r right!! It is not rooted... here my recovery View attachment 2857903
Click to expand...
Click to collapse
OK This means you have full stock rom and stock recovery. Only thing you have that you might not want is an unlocked bootloader, which you need root to fix. Do you want me to "Try" to and help you do tht or are you just going to leave it?
Are you sending it to google or LG?

rootSU said:
OK This means you have full stock rom and stock recovery. Only thing you have that you might not want is an unlocked bootloader, which you need root to fix. Do you want me to "Try" to and help you do tht or are you just going to leave it?
Are you sending it to google or LG?
Click to expand...
Click to collapse
Would be very nice if u help me!!! Do you think its possible without USB?
I dont know if I have to send it back to google or LG? I bought it over the play store from Germany to Austria!
I think my warranty is lost if I send it back with the open bootloader... am I right?
regards

w1m9 said:
Would be very nice if u help me!!! Do you think its possible without USB?
I dont know if I have to send it back to google or LG? I bought it over the play store from Germany to Austria!
I think my warranty is lost if I send it back with the open bootloader... am I right?
regards
Click to expand...
Click to collapse
Google will not reject warranty of hardware failure due to unlocked bootloader. LG might. If you bought it from google, it usuall goes to google, but not sure if changign country changes things. Best to ask google.
Only chance to lock bootloader is to get root by using towelroot. It may or may not work.
https://towelroot.com/tr.apk
Run the app. It is supposed to reboot but sometimes it does not. If it does not, reboot yourself. Then ipen SuperSU and check if it has root.
If it does have root, install bootunlocker https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en - and reset tamper flag and lock bootloader. Then unroot using SuperSU.
If towelroot doesnt give you root, you cannot lock bootloader

rootSU said:
Google will not reject warranty of hardware failure due to unlocked bootloader. LG might. If you bought it from google, it usuall goes to google, but not sure if changign country changes things. Best to ask google.
Only chance to lock bootloader is to get root by using towelroot. It may or may not work.
https://towelroot.com/tr.apk
Run the app. It is supposed to reboot but sometimes it does not. If it does not, reboot yourself. Then ipen SuperSU and check if it has root.
If it does have root, install bootunlocker https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en - and reset tamper flag and lock bootloader. Then unroot using SuperSU.
If towelroot doesnt give you root, you cannot lock bootloader
Click to expand...
Click to collapse
Thank u man! U r the best! Everything worked well.

w1m9 said:
Thank u man! U r the best! Everything worked well.
Click to expand...
Click to collapse
No problem.
Sent from my Nexus 5 using Tapatalk

You can flash stock recovery via the TWP app, which allows this
#64268gkyJL#8653%dhjGUKVS357.

howard bamber said:
You can flash stock recovery via the TWP app, which allows this
#64268gkyJL#8653%dhjGUKVS357.
Click to expand...
Click to collapse
He already had stock recovery.
Sent from my Nexus 5 using Tapatalk

want to roll back to original one..
currently i have cyanogen recovery .i wanted get back to the original software(ie, same as the nexus 5 out of the box(which is not rooted and can get os updates from google(OTA)).can u please suggest me the procedure required for it???

[TOOL][DAISY] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Xiaomi Mi A2 Lite's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​

Yay ^_^ Thanks for the efforts Respected devs. Hope it makes life way easier for people here at the community ^_^

unlock bootloader and root still delete all of my files right?

machine1104 said:
unlock bootloader and root still delete all of my files right?
Click to expand...
Click to collapse
Yes

Xiaomi Mi A2 Lite got messed up
Hi there!
I have just received my new Xiaomi Mi A2 Lite phone and wanted to pass all of my data from my old phone to it in a way that it was required to be rooted.
KingRoot didn't work on this new phone, so I unlocked bootloader and tried to install TWRP recovery on my phone.
Installing to the recovery partition did not work. I searched the error it gave me and found a thread saying that flashing it to the boot partition worked for them. So I did. Next thing that happened is that my phone did not boot into the OS (operating system) ever again. It only booted TWRP.
I have since been able to remove TWRP (though I made a back up of it) but the phone still stays on just the loading part before going to the OS.
I have since been able to get back the fastboot and stock recovery, but the phone will not start into the OS anymore.
How can I fix this?
I have been searching for ways to restore my android to the 8.1 Oreo version that it was.
Can I do it with this Tool All In One? Please help! Thank you in advance!! Much appreciated!!

hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?

chillout23 said:
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
Click to expand...
Click to collapse
If you need to flash twrp and root.no, you will not lose data

Ok. Thank you very much for answer
Then will try

chillout23 said:
Ok. Thank you very much for answer
Then will try
Click to expand...
Click to collapse
I would suggest using the root method mentioned here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Twrp does not have good results for most people.

With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway

chillout23 said:
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
Click to expand...
Click to collapse
If your bootloader is unlocked, you should not lose any data just installing magisk

Yes...my fault. My BL is unlocked already.
But I posted in that thread...because of some reason does not work. But this is not thread about it
Thanks for help

So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device

chillout23 said:
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
Click to expand...
Click to collapse
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again

uptowner said:
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
Click to expand...
Click to collapse
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem

uptowner said:
Because your not supposed to install the twrp image just boot from it
Click to expand...
Click to collapse
Installed TWRP image. I know what is .img

mauronofrio said:
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
Click to expand...
Click to collapse
oops sorry i should check what thread this is before trying to answer a question i blame alcohol .
Thing is there are posts out on the net that advices people with the a2 lite to install the twrp image to their inactive slot and not to just boot it and that's where things seem to start going wrong.
This has absolutely nothing to do with this tool and sorry i just dived in here and confused people.
maybe some kind passing mod will get rid of the post apologies again

Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.

mesuahas said:
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
Click to expand...
Click to collapse
Read the op follow it exactly how it says if u don't know something research it.i have root with no problems if u do as the op says u shouldn't have no problems

Will this work on pie at all?

Question Serious brick? Help please!

I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.

Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!

toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well looks like I can go into the bootloader but if I choose recovery mode it just goes back to the "Device is corrupt screen".

toyanucci said:
Try using the button combination at not to get to dock recovery and try to wipe and reset the phone there or try this is that doesn't work (you may have to unlock the bootloader to do it). I had the same error when I restored my OP7T to stock and relocked the bootloader. I don't remember exactly how I fixed it but I did in the end do don't worry, all of not lost!
Click to expand...
Click to collapse
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I don't have a backup of the tmobile rom :/ I think we ned the modem files from the tmobile version, which would be on my phone yet if I could acess them? The last time I did anything with a phone was the OP6 I'm out of my depth...

hiryupd said:
Well I rebooted into bootloader but when I select Recovery mode, it just reboots back to the "Corrupt device" message. Not sure what ROM to use here as I dont have a backup of the tmobile rom :/ The last time I did anything with a phone was the OP6 Im out of my depth...
Click to expand...
Click to collapse
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom

toyanucci said:
The instructions in the link I sent will work but I'm not sure if there's a t-mobile rom that's available and I'm not 100% sure you can just flash the global rom
Click to expand...
Click to collapse
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/

hiryupd said:
I'm really not sure what to do atm, I don't want to make worse issues but It looks like its not a total brick at least? It should be fixable if the tools are around. I've read that we cant just flash global because the modem wont work with our phones? If i could access my files I could back those up I'm guessing? But messing around was what got me here. I just want to get stock back now. :/
Click to expand...
Click to collapse
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember

toyanucci said:
People use the word brick a lot but I've never actually had a completely unfixable issue with an android phone. It can be fixed for sure with the right rom.
Oh, you can also try unlocking the bootloader. Since that was the only change you made it might boot. I'm remembering I had tried that too and it may be what got my phone to boot back up but I can't remember
Click to expand...
Click to collapse
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....

hiryupd said:
Yea that occurred to me as well. I tried it and it worked! So at least I'm operable. But its just kicking the can down the road. Id really love to just be able to get back to stock and be done. But Im guessing that the boot.img from the oneplus site was the culprit. I don't have the original tmobile rom payload dumped. So I'm just going to site here with an unlocked phone I cant update... I dunno. Appreciate your help bud or i'd still be flipping out....
Click to expand...
Click to collapse
I got it done with the 7T so it can be done and if you had restored the stock boot image with magisk before you uninstalled it then you are stock, just with an unlocked bootloader.
Re updates, again if you have the stock boot.img restored you'll get Ota updates just fine.

hiryupd said:
I'm on a T Mobile OP9 and had removed Root today via Magisk. Then deleted Magisk. All was fine. I restored the boot.img for the 11.2.2.2 and rebooted again, all good. I then went to 'fastboot flash oem lock' and it wanted my unlock token, I uploaded it to adb and retried, adb said finished and I looked at my phone and immediately saw in red "your device is corrupt it cant be trusted and will not boot". So yea. Im sitting here not sure what I can do. Its a TMobile OP9 and I just wanted to get it back to stock.
Click to expand...
Click to collapse
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.

inspron said:
Do you have a backup T-Mobile stock oneplus 9 regular boot.img image? I can try a few things on my end if you want me to help you test. I forgot to take a backup of the boot.img. If you can share that I can try to help. I plan to return to stock too.
Click to expand...
Click to collapse
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?

hiryupd said:
Thats the thing I used a tutorial from early on when the phone released, so I downloaded the 11.2.2.2.LE25AA and I used payload extractor to get the boot.img and rooted with magisk. So that was my backup. I assume this is why locking it now makes it corrupt? Im currently unlocked but also unrooted. There is no boot.img for the Tmobile variant floating about?
Click to expand...
Click to collapse
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image

toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.

hiryupd said:
Right and thats what i did. So what would cause my relocking it to be corrupt? I followed the procedure i wrote above. My rom is stock t-mobile except for the boot.img from the OP rom. So im sitting here on unrooted but also unlocked, unable to do anything in the way of relocking the loader. Im assuming at this point I just need to wait for an MSM tool for the non pro tmobile version.
Click to expand...
Click to collapse
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.

toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Well system update always comes back saying it has a problem and cant update. Also yea after I relocked It has a dialogue asking if im sure because it will do a full wipe, just like when I unlocked it. But instead of doing the full wipe it booted into that red text about being corrupt. So right back here again

toyanucci said:
I always root this way...
fastboot boot boot.img
Then let magisk backup the stock image before patching it and applying it so if you ever need to go back to stock, magisk can restore it.
fastboot flash boot boot.img doesn't allow for magisk to backup the stock image
Click to expand...
Click to collapse
I wish I had seen this part prior. I flashed img about 3 weeks ago prior to this method was known to me.

toyanucci said:
The procedure is to root and unroot back to stock. For relocking I'm not sure why the error happens but it happened to me as well. I know after relocking you have to wipe the phone for it to work so I can only think maybe it has something to do with stock recovery
You wouldn't need MSM tool but a full stock firmware would be flashable via the method I put in my first reply in this thread which would wipe the phone then flash every partition from the stock rom and would get you back up and running.
For now though for Ota updates you just need the stock boot.img for the os you're on.
Click to expand...
Click to collapse
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.

inspron said:
Thank you. Hopefully someone can share the stock boot.img for the T-Mobile variant.
Click to expand...
Click to collapse
I exported them a while ago on a thread, we just moved our company so i dont have those systems and drives set up for me to get on server. We unbrick and all that fun stuff. If you have a telegram send me the info. & ill add you to try to resolve your issue.

Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...

oh
hiryupd said:
Well i see now in the developer options that my OEM unlocking "Bootloader is already unlocked" and I cannot change this as it is greyed out? I dont if that means anythig for any of my issues...
Click to expand...
Click to collapse
if that's the case you can flash with official build, and then you can add the t-mobile bloatware if you want.. Which i take it off most phones by request.
Official Build (Direct DWLOAD)
(Stock - Boot.img (Direct DownL)) Instead if easier...
If you really want the bloatware back that makes T-Mobile T-Mobile then.. here ya go..
pm install -k --user 0 com.mobitv.client.tmobiletvhd
pm install -k --user 0 us.com.dt.iq.appsource.tmobile
I want T-Mobile Boot Up Animation! I Want People to know im using T-Mobile!!
Here ya go, "https://www.hongkiat.com/blog/change-android-boot-animation/" - Add Sound even
{
"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"
}
I Hope this helps ya mate ..
You can also use these files I built to follow this post too if you need more help.
BACK TO STOCK 1+9