Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
Hey,
what a day, searching whole night how to get my phone back to life but nothing is happening. Somehow i did managed to birck my mi4c. I tried to install custom ROM with TWRP I think 'miui_MI4c_7.1.20_e887ff73d2_7.0' it finished like in 2minutes and asked me about rebbot or wipe data. Choosed reboot and only mi logo appeared.
Since then I cannot go back to recovery TWRP i had 0.3.1.0.0 version(did update today previous one was old like 0.2.8.3.0).
My phone previously was running on cyanogenmoed 12.1**with anroid 5.1.1.
The only options i have now i to go in fastboot.
Somehow ADB dont find any device now, tried all kind of versions and still the same.
I have no luck with xiaomiflash/miflash either, the program finds my device but dont flash it.
Tried too with many versions (old and new ones) but no luck....
Error:
The system cannot find the file specified .(0x800700002: flash_all_except_storage.bat)
Tried with all three options (flash all, flash all except storage, flash all except data and storage) but is giving me the same error..
I did download a few images .tgz
libra_images_7.1.4_20170104.0000.00_7.0_cn_a4e850e718
libra_images_6.1.7_20151221.0000.11_5.1_cn
libra_images_V8.2.3.0.NXKCNEC_20170407.0000.00_7.0_cn
Check for space extracted with winrar, renamed too...still same old problem.
Tried to solve with the QFIL (Qualcomm_Flash_Image_Loader), but I cant see my device there...
Drivers I think are correct one (I think)
I think i did something stupid**(
Or I dont understand what i am exactly doing...
I would really appriciated any kind of help, thanks!!!!
4Cvetko4 said:
The only options i have now i to go in fastboot.
Somehow ADB dont find any device now
Click to expand...
Click to collapse
But in fastboot mode you DO NOT use the ADB command, only "fastboot.exe" (on Windows). Do the following:
get fastboot
extract "fastboot.exe" and the DLL files to the folder with flash_all_except_storage.bat
run flash_all_except_storage.bat
:good:
SOLVED!!
with this en . miui . com /thread-255776-1-1 . html and Minimal ADB and Fastboot
then i flashed it.
Now that i installed this ROM 8.2.3, it contains half english chinese apps and ofc no google apps which for me is useful.
I did unlock it via miflash_unlock(asked for unlock some days ago), and then uploaded twrp recovery.
But when I go in recovery mode there is some chinese words and three options (screen is blue-black), you can select via up and down volume and confirm with power button.
No idea why there isnt a twrp recovery.
thanks!!
Congratulations!
Hi everyone,
I'm quite new to unlocking and rooted phone, but I've read many many post on this forum but nothing worked....
Here what's happening;
Few days ago I wanted to Recover from TWRP a backup that I've made. I launch the recovery from TWRP (important details, it was a backup that I made from slot B in twrp....) in slot A.
So yes I indeed restore a slot B recovery into the slot A in TWRP.....
And I tried to reboot after that..... and the problems begins !!
I just have a blackscreen with a blue light, nothing happened..... Same thing If i try to boot into recovery mode.....
Since I tried many many things but nothing worked...... I can't boot into TWRP from fastboot.
When I'm trying that:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
The phone just reboot and got stucked on the screen with one plus logo and the text "fastboot mode" below the logo.....
I read all these post below and everything I tried (erase all data, change the active slot on fastboot mode......)didn't work:
https://forum.xda-developers.com/oneplus-6/help/oneplus-6-os-twrp-stuck-fastboot-screen-t3870989
https://forum.xda-developers.com/oneplus-6/help/stuck-fastboot-rooted-help-please-t3851802
This one I didn't really understand exactly what needed to be done but I guess I need to boot into a custom recovery as well:
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Even tried that but it didn't unbrick the phone:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I tried to boot into another recovery, but same thing not working/booting;
Code:
fastboot boot blu_spark_r65-oos-pie_op6_9a5f932e4.zip
So I'm desesperate and really really need help !!:crying::crying:
Does anyone can help me step by step or has a solution please?
I can access to fastboot mode that is the only think I can do and the bootloader is unlocked.
Go and see there :
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
You'll get your phone like it comes out of the box.
yep, do this:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
I had the same problem with my OP3. i cant get past the fastboot screen. after i tried the tool everything was back to normal. but i had to oem lock after it to boot up.
Also use the official twrp for a fully functional backup and restore
Thank you all for your reply !
I've tried to follow the process from the link but the MSMTool is not finding my OP6 and I've uninstall in the Device Manager as indicated:
HTML:
plug in the phone to the computer, go in device manager and under port (COM) disinstall qualcomm one (oneplus 6) and then unplug
But When I go into safe mode and re-plug, I can't do this part because I don't have this information....
HTML:
Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process
I tried on 2 different PC (Windows 10 and 7) but nothing worked so I can't used the MSMTool
You have to use it in safe mode to install the unsigned drivers. It only works when you see the device as something like 9800 in your device manager.
Dont worry if it fails a few times. I had to do this 8 times on my OP3 till it was successful.
You can also use this guide:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
The steps are the same
EDIT: I attached a zip with AIDA64's reports for this phone. One report has Magisk hidden from AIDA64, the other doesn't.
This mostly a copy of _cab13_'s Rooting the UMI F2 post as the same instructions for rooting that phone are how I rooted the S5 Pro. So please give _cab13_ thanks here if this helped you root your phone. I'll take a thanks for removing the orange state warning if I helped you with that
Please be patient when posting questions, I will get back to you as quickly as I can. I just have many responsibilities which take up a great deal of my time.
Rooting the S5 Pro
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEI['s]s and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never re-lock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like boot loops, if that happens to you, don't freak out! Simply re-flash the stock ROM, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
[Non European] UMIDIGI_S5Pro_20210107.V3.04
[European] UMIDIGI_S5Pro.E_20201130.V3.04
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
UMIDIGI Community Forum S5 Pro Thread
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your package manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode. Unplug your cable from your phone
and replug it after fastboot is printed at the bottom of the screen.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_S5Pro_20200702.V3.02 (or the European one) with SPFT by selecting the scatter file, pressing download an rebooting the phone
(Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) In the following code, the vbmeta.img and the recovery.img are the stock files from the ROM you downloaded and extracted.
Code:
fastboot erase boot
fastboot --disable-verity --disable-verification flash boot magisk_patched.img
fastboot --disable-verity --disable-verification flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory. Refer to Flash Tool guide if needed.
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition. MAKE SURE FORMAT IS NOT SELECTED!
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
ONE LAST THING
Get rid of your orange state warning.
Download the attached zip file and extract.
Put your phone into fastboot and:
Code:
fastboot erase lk
fastboot erase lk2
fastboot flash lk lk_patched.img
fastboot flash lk2 lk_patched.img
fastboot reboot
No more orange state warning! Reflash the stock lk before unrooting, though.
ATTACHED LK FILE IS FOR UMIDIGI S5 Pro ONLY.
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Hey guys it's me again !
Got some good news : I bought a S5 Pro as well
And I ABSOLUTELY LOVE IT !
I might get into rooting it soon, idk.
Thanks for the shout-out @zerosava
hermeez said:
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Click to expand...
Click to collapse
No luck for me finding a custom recovery (twrp or anything else.)
If you have any exp with them, see if you can make the F2's (found in the F2 root thread) work. It SHOULD only need a minumum of tweaking, just to account for the (afaik) slight soc differences. i'm not gonna hold my breath. there seems to be a void when it comes to enthusiasm for this phone. by my serial no, i have the 4832nd phone manufactured. compared to serials ranging from 22000- 189000 for my other umis (f1play, s3pro, f2, power3)
I think I'll try making TWRP soon for it.
The F2 TWRP would not be usable this easily, it's easier to start fresh.
If anyone wants to try, download the sources for the F2 TWRP on my GitHub, then you need to extract the stock kernel and replace the F2's with the S5pro's
root working thanx
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
Sorry, but I made this clear in the original post:
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
I do not know how to help you. My only suggestion is to post your problem in UMIDIGI's forum here: UMIDIGI Forum
If anyone can help you, that's where to find them.
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
I am sorry, but you will have to contact UMIDIGI support. Only they can help you as far as I know. I feel for you, I really do. I did this when I was a newbie with my F1 Play.
QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1
Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
stick2020 said:
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
Click to expand...
Click to collapse
Do a "download only" flash of the "super", " vbmeta_system", and "vbmeta_vendor" partitions only (uncheck all other partitions) from the previous ROM. That should do it.
ZeNNoP said:
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
Click to expand...
Click to collapse
What precisely stuck you?
There is a new update firmware please make a rooting tutorial on youtube.,
Somebody made a custom TWRP and posted it on here. So if that'll help anyone out and get them to make a tutorial video, that be great. 'Cause I'm reading this over and over again, and I think I can do it, but I'm being very hesitant about it. And it's getting me all frustrated. I had it on "Flash Mode". And when I continued typing it out, it didn't go through and that had me on a raging panic attack. Luckily, it didn't mess up. But now I'm more hesitant. Please make a quick tutorial, doesn't even have to be perfect...
TWRP is at the bottom of this page:
[MT6785]How To Root Umidigi S5 Pro And Install TWRP 3.4.0 Recovery ~ Techswizz
To Root Umidigi S5 Pro, we will be using the Adb Tool Mode with TWRP recovery for Umidigi S5 Pro. It will be wise to read the post very well before flashing the recovery to avoid any Device errors or brick.
www.techswizz.com
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
bmaz121 said:
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
Click to expand...
Click to collapse
I am able to get FastBoot Mode on my screen (through step 6). I plug the phone back in per directions & I hear the Windows device connected chime.
I type: fastboot flashing unlock in the same cmd window
and I get "<waiting for any device>" in the cmd window and it hangs.
Every few seconds I hear the Windows device disconnected noise, but no device connect chime. This lasts indefinitely.
I repeated step 7 several times with variations with the Vol+ button: pressing first, holding down while pressing enter in cmd window, pushing afterward, holding down afterward, etc. Same results as described above.
Any help available? Should I not unplug my phone from the PC? The F2 directions did not require that.
thanks!
Hi guys Zeph here.
I've just rooted my Redmi Note 4 without any problems. I've tried to install several custom ROMs like HAVOC, Pixel, etc using TWRP but it showed some error I don't know. My backup ROM did not install so I've tried to install Global Stable ROMS from Internet but those were shown as corrupt. I've also tried using fastboot, ADB sideloader but same problems are happening. So basically my phone is just a hollow without any OS. Any solutions please because that is my only phone.
Here are some screenshots..
Can you boot up normally?
If not what happens, when you try?
gabtit7 said:
Can you boot up normally?
If not what happens, when you try?
Click to expand...
Click to collapse
Sorry when the backup ROM didn't get installed I had completely wiped all data for sake of installing Global custom ROMs. But it still didn't get installed. So my phone is like DOS without any OS.
Oh. Well thats a problem.
First of all:
Go to https://c.mi.com/oc/miuidownload/detail?device=1700309
dowload the rom (its a zip) and transfer it to your phone
go to twrp
flash it with twrp
reboot to system
Now if (while booting up) it says "The system has been destroyed":
Just keep booting in twrp, back to system, back to fastboot and repeat for some time and multiple times a day. For some reason thats how you call the autorepair to wake up, it will remove the ROM you just installed and probably install a backup one on its own
If this doesnt work too:
I will suppose you have a pc with fastboot & adb drivers available
Since the phone is alr in deep s***, lets try something quite risky
1)
go to twrp > wipe > format data
2)
connect your phone to pc while in fastboot
and execute these commands
fastboot erase system
fastboot erase cust
fastboot erase boot
fastboot erase vendor
CAREFUL: NOW YOUR PHONE IS BRICKED, BUT FIXABLE (probably)
3)
repeat the steps on the top of this message
All this should fix the problem, if not i am sorry but the phone will be unrepairable without any professional technician