Related
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
jadkar said:
- This is pretty much an exact duplicate of a thread I posted on Xoomfoums, but I think it maybe better here...
Anyway, really looking for a miracle!! I got my xoom back from Moto yesterday for the 4G upgrade and I tried to root the device the same way I have done before. I got as far as unlocking it. The last thing I flashed was a “bootloader_patch” from a guide on Xoomforums. Now I’m stuck and I only found one person who had this issue …… he returned his device for a new one
So summary thus far.
- I can get into Fastboot support and flashing always yields “success”.
- I seem to have no ADB connectivity. (don’t know if I really need it for fixing this issue since I can fastboot and flash).
- I have tried, stock images, CWM recoveries, rogue recoveries, also some HLK75 imgs, etc!! All leave me at the same place.
Where am I stuck:
- I reboot and let it go normally and she hangs at “Moto screen”
- I reboot and tap the “volume down” leaves our three choices….
-- Android recovery -> tried to enter recovery and sits at the famous “Reading ODM fuse:1”
-- Fastboot -> That works, I can flash from here OK
-- RSD support -> Haven’t played with that, I have read people going to dark places when they screw with this. If I have to I’ll do so carefully.
All the methods of going back to OEM are epic fails. Nothing new happens, but I am always left with the same result.
Any help you could lend would be greatly appreciated!! I really would rather truck through this than return it however I’m afraid if I don’t get rid of it soon it will be harder for me to make an excuse to the retailer.
Thanks - John
Click to expand...
Click to collapse
When it sits at "Reading ODM Fuse1" can you press power to see if it will select that option and take you into CWM recovery (assuming you have that installed)?
When you say you are flashing from fastboot protocol, are you connected to your pc? What are you flashing? I'm a bit lost with your description...
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
jadkar said:
^^^
Thanks for the reply. Good suggestion on the power button.. press as its sitting at "Reading ODM fuse:1" but....... not good
So I didn't list all the things I have flashed because I tried many many fixes from multiple guides. I could look through all the links if you want the exact names but none of the made a difference. Yes, flashing from my PC connected via USB.
So after the first root guide blew it up I tried to flash a bunch of recoveries and system images. I also tried to bring her all the way back to OEM using the appropriate guide. No matter what I flashed I was given a successful message but it still gets stuck at the same screens. Nothing gives me any different results. I'm wondering if the actual bootloader is hosed. If so can you flash a new bootloader?
Here's some stuff I have flashed along with some links....
recovery-Tiamat-R4c-100611-1150-cwm.img
MZ600_HRI66_OEM_Image
how to root guide that I origianlly followed.... http://www.xoomforums.com/forum/mot...ow-root-3g-4g-wifi-only-xoom-stock-3-1-a.html
Someone got the build img after the LTE upgrade, so I tried this....
http://www.xoomforums.com/forum/xoo...rade-stuck-recovery-reading-odm-fuse-1-a.html
I also tried from fastboot erasing all the partitions before I flashed them and that didn't help.
Thanks for your time!!
Click to expand...
Click to collapse
Well, you are flashing wildly but not well, (JK)
This thread should help you:
http://forum.xda-developers.com/showthread.php?t=1299485
Here is a great post by Saintfyre (I think it fits the bill):
"Yeah join the FUBAR Club.
I was in the same boat as you did the same thing.
I now have my Xoom back to HLK75C and have 4G/3G and Wifi connectivity again so all is not lost!
What I did to fix my situation:
-I wiped the Device and just went through Solarnz's Root Method here: http://forum.xda-developers.com/showthread.php?t=1074979.
-Download the HLK75C (This is the build the 4G Xoom's shipped back with) file that AceXMachine provided here, post #6
-Extract the File to your Android SDK Platform-Tools folder, password is AceXMachine
-Follow his instructions to apply the images. I copy pasted but all credit goes to him for putting this out there.
On Windows shift and right click the Platform-Tools folder -> Open Command Window here.
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
After following all of this I had my Xoom back just like it had come back from Moto after the upgrade. I've since then flashed the Tiamat Tachi OC GPU Kernel to have Overclocking again. No issues since then, have full 4G/3G Connectivity and Wifi has no issues as well."
From this thread:
Yup.....I tried that one as well, it didn't work either.
I really think the bootloader is shot. Is there a way to repair it? I think what killed this was the last .zip file I updated as part of the root guide I was using, it was "bootloader_patch.zip" found here..... Bootloader_patch Does anyone know what this does??
**edit: Is the boot.img the bootloader?? If so ... forget it as I already tried flashing a couple new ones during my attempts to bring it back to OEM.
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
jadkar said:
So my logic now is rather than keep flashing like crazy let me try and get recovery working. For this I will try and erase everything using fastboot (my only option) and then flash a boot.img and a recovery.img
Questions:
- Will keeping everything earsed from the device except for a boot.img and a recovery.img allow me to get into recovery? I want the minimum amount of partitions flashed. I want to just work slowly and systematically trying to get into recovery first.
- I do not have ADB support, can this be a hint? Shouldn't adb support be working or do you need to have somthing in the system / app partition for ADB to communicate with. I know its called Android debugging bridge so the name makes me believe that I need an android OS loaded and this is why my ADB doesn't work.
Please take a look below and let me know if anyone has any suggestions on different boot.img or recovery.img Ihave not tried. Also, I'm wodnering which ones I should try in combination.
Going forward I'm going to keep track of each combination I try as to avoid duplicated / wasted effort.
recoveries I have tried:recovery-Tiamat-R4c-100611-1150-cwm.img
recovery image from steady Hawkin (3g/4g Stock Images for HR166)
Rogue-recovery image from rogue-recovery-1.2.0
Boot images I have tried:boot from steady Hawkin (3g/4g Stock Images for HR166)
boot from AxeMachine HLK75Csystemboot
boot from AxeMachine HLK42Bsystemboot4g
Click to expand...
Click to collapse
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
okantomi said:
How have you flashed zip files without ClockworkMod recovery? It's hard to brick a Xoom but you may be close.
If there is anyway to flash your device's stock images through fastboot, that is your best hope at this point.
Click to expand...
Click to collapse
Yeah, so I have another thread running on xoomforums and I have explained over there that just about 30 minutes ago I erased everything and reflashed the "HRI66" files. I used everything from that build so there was just the stock recovery, etc. I even did a fastboot oem lock. This didn't work either.
After this I was able to return to fastboot and "unlock", so now I am just back to where I was before.
Me and one other dude think I have a corrupetd / damaged partition or semi-destroyed bootloader. The thing is I can't get an answer to a real simple question.....
is the bootloader a "flashable" component?? I'm not sure if the boot.img IS the bootloader or the bootloader is something else that's not flashable at all. If the later is true then maybe my bootloader is FUBAR.
Thanks!! John
I'm the other guy jadkar was referring to from Xoomforums. He's pretty much put it succinctly but here's my version
ggrant & fish over at Xoomforums suggested we PM solarnz (etal) or post over here for help. I am writing this for myself and another Xoom user. We've both sent our Xoom's to Moto for the 4G upgrade, received them back with 3.2.2, and then proceded to root the wrong ROM over the top. The result was a hang at the red Logo. In hindsight, we should have used Universal Root.
We've both exhausted the experience at Xoomforum (hence our plea here Anything you can suggest would be most appreciated. Personally, I think something is awry in the recovery partition size (perhaps changed by Moto at the upgrade?):
To save the basic suggestions off the bat, we've done the expected already: Installed moto's drivers, tried new cables, AND an entirely different computer. We've tried completely erasing boot, system, recovery, cache and userdata partitions, and flashing back the stock HRI66 images with fastboot.
ADB doesn't recognize the 'devices' command, only fastboot see's the Xoom. Accordingly, the only way to get into fastboot protocol is to Vol Up + power, and wait the three seconds and toggle. We can both toggle (with Vol) into Recovery, RSD and Fastboot). After flashing MULTIPLE flavours of Recovery images, the result is always the same: Recovery hangs reading fuse: 1. There's never the Recovery menu or graphic of the the Droid robot.
As for RSD, I've tried all the way through RSD Lite 5.0 with the thought of using solarnz' (I think) recovery.SBF. The result there is always the same as well: By toggling into RSD mode (Vol+Power into RSD), RSD Lite see's the device OK, but shows an error stating initialization values cannot be read. Note this occurs immediately upon plugging the Xoom in, even before TRYING the SBF file, which BTW, fails even if you try.
Via fastboot, we can oem lock and unlock (note however that in the command window, it states that it failed due to too many links, the the action seems to have worked on the Xoom anyway.)
So, it's down to THIS; the common thread for both of us is that we cannot successfully get into recovery, no way, no how. Again, ADB won't recognize the Xoom, only Fastboot
Any help would be APPRECIATED!
P.S. John, if we don't get help here, I have a 9mm with two spare rounds (for the Xoom's, not us!)
^^^
Thanks .... we'll see if anyone bites.... I hope so
As for the 9mm ........ Thanks but I have a flight this morning and I'm seriously thinking about dropping the Xoom out my plane from lets say 3500ft!!
LOL! Safe flight.
Guys, you all are crazy!
I appreciate your resourcefulness, but it sounds like you're almost out of options, lol.
If you can get to 'starting fastboot protocol' you are not bricked. If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Found out another guy tried 2 different PC's and it did the same thing. He even reloaded android sdk. He decided to try a 3rd PC that he had to load sdk to. It worked! So he found there is an issue somewhere with his 2 PC's sdk or windows install. When I got my xoom in June sdk would see it, but I never rooted at that time. However I did update and install all the new stuff for sdk.
Sent from my Xoom using xda premium
okantomi said:
Guys, you all are crazy!
Click to expand...
Click to collapse
Probably... That's half the fun!
okantomi said:
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Click to expand...
Click to collapse
Most assuredly. I develop Android apps with Eclipse. I know how to use SDK.
okantomi said:
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798
Click to expand...
Click to collapse
Too late, mayhem already commited!
okantomi said:
What I can't find at this moment are the 4G stock image files.
Click to expand...
Click to collapse
That would be the ONLY thing we haven't tried. I know how to lock/unlock, flash images, etc. We've both done all of your above instructions to the letter. I've already replaced my Xoom and it's at Moto having 4G surgery, so I can't do any more of this now. John will have to try again, but as (I hope) you've already read above, the status quo techniques are not working.
Any clues about why a successfully flashed recovery image isn't working?
okantomi said:
..... If you cannot connect your Xoom via adb while your Xoom is in fastboot, it usually indicates that there is something wrong /missing from your setup.
Are you sure you have all your moto drivers installed and the proper image files in your platform tools (or tools folder) and you are actually in the right directory when opening the command window?
Please try to follow the instructions in the following
thread before you commit mayhem on your innocent Xooms.
http://forum.xda-developers.com/showthread.php?t=1249798 for setting up everything you need to ensure that adb will work and a proven method to install cwm recovery and root once you have been able to get back to a proper stock image. What I can't find at this moment are the 4G stock image files. You need the following to flash through adb/fastboot: system.img, boot.img, recovery.img, and userdata.img.from the Honeycomb 3.2.2 4G Xoom.
Commands to use:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Don't give up...good luck!
Click to expand...
Click to collapse
Lots of stuff to answer back here, please don't mind the bullet points....
from your guide... "Did your device not show up? Make sure that you have USB debugging enabled in Settings/Applications/Development on your Xoom."
- I have no devices connected when typing ADB devices and based on the above how can I make sure I have USB debugging enabled if I can't even get to the Android OS??? I have fastboot support that's it, I don't think its possible for me to get ADB to connect with all the partitions erased. ADB or "Android Debugging Bridge", the name implies you NEED android on the device to use it. I don't have android since the system partition was erased.
- I have two different 4g images from AceXMachine's posts. However his build posts only have system.img and boot.img. So based on your instructions I need to know what userdata.img and recovery.img I should use.
- I keep asking and I will continue until I get an answer on the next question..... I think the bootloader is screwed up. I want a new one (or at least the one that came from my 4g upgrade). Where can I find one? How do I flash it? Is this synonymous with the boot.img?
Thanks!!!
Well, your issues are way, way, way beyond the scope of my limited knowledge, lol!
Have you tried to chat with the developers on #Xoom on freenode.net? Bigrushdog and solarnz are both really nice and so is SteadyHawkin, if he's on there. Someone may be able to help.
Good luck!
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
hammer4203 said:
Flash it back to stock moto!!!! Then start over with bringing your xoom to 3.2.2!!!! That is why you can't get anywhere! You keep killing off everything! AceXMachine did the same as you and he has his xoom back to 3.2.2. Or send it to moto and pay them to flash you back. You are not doing it right period! You have posted the same issue and people have tried helping, but you seem to want to keep going into rsd and other crap you don't need. The baseband is in the boot.img. Flash the hir66 then update to the hlk75c.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
mmmkay... well THAT was a little terse. Don't you think returning to the HRI66 stock was the FIRST thing we tried? We downloaded the stock images from the provided links, checked the MD5, and then did this:
adb reboot bootloader
Xoom will then reboot into bootloader screen
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Use volume rocker to select ok and then xoom will reboot. At this point you should be back to a factory state which includes being locked and unrooted.
Click to expand...
Click to collapse
Isn't THAT what you suggested? Yes? No?
^^Hammer....
I know this threads is really long and probably didn't read all of it (don't blame you) but a while back I explained that I did try and flash everything in Steadyhawkn' HIR66 build. I flashed the 4 images included (boot, system, userdata, recovery) I also went as far as an OEM lock at the end. This did nothing. I tried this a couple times.
Can someone lead me to the patience pool; I need a drink.
ACTUALLY I GOT THE ANSWER TO THESE QUESTIONS (ignore this thread)
I've been reading through this guide: http://forum.xda-developers.com/showthread.php?t=1249798
Question 1: When they say wipe everything, do they mean media too? (like music and such) Because when I had a samsung vibrant, they also said that but it never wiped media.
Question 2: Will I have to run a nandroid backup if this is my first time rooting, or will it be unnecessary?
Question 3: After finishing doing everything (unlocking and rooting)
do I just directly flash this http://forum.xda-developers.com/showthread.php?t=1484770 or is there something I need to do beforehand?
Also, in the guide, it says something about green android of ! if you have received an OTA. Which I have received many from Moto before. Will I have to download the original motorola files (HC or ICS, I'm currently on ICS)? If so, where do I put it? I'm confused
okantomi said:
"The green bot of !
there is one problem that exists with all xoom roots/cwm hacks. I had this problem as well as a bunch of other people when trying to flash CWM. If these files are present after an OTA update, then your xoom when entering recovery will show the green android robot with a exclaimation point instead of CWM.
If you have applied an official ota update.zip then you have a file like this on your xoom that will prevent CWM from working:
/system/recovery-from-boot.p /system/etc/install-recovery.sh
From the command window, type
adb remount adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above.
Click to expand...
Click to collapse
Thanks so much! I'm new to this, it's so much different from rooting my Samsung Vibrant phone
cmd hangs
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
rosystreasures said:
"Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Do not relock! After your Xoom boots back up and goes into the setup screens skip setup and enable usb debugging.
Proceed to Step 4.1, above. "
I did the above steps. All my command prompt does is hang...waiting for the xoom to respond.
Click to expand...
Click to collapse
There may be something wrong with my instructions...they've gotten convoluted over time. Try one of the other guides in General..there are a couple of newer ones that might work better. Mine still gives a lot of information but I think I'll retire it 'cause I don't want to cause issues.
I recently rooted and flashed a rom on my xoom. I'm a simple point and click windows user and I didn't have much trouble, so it's not that hard to do.
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
http://forum.xda-developers.com/showthread.php?t=1477024
is the thread I used. Follow the instructions exactly and read the entire thread before you start, it'll save you a few headaches. This'll get you in (I think) ICS with superuser and all that jazz. If you want a rom, like me, then you'll have to head over to the development forum and take your pick. I'm running EOS 2.0, still deciding what to do with my xoom atm.
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
rosystreasures said:
I wish I'd known of this thread last night. I struggled for several hours to root. It finally did. I also got the rom installed.
Click to expand...
Click to collapse
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Quickboot vs. ROM manager
okantomi said:
I'm glad you got it rooted. That newer guide skips some steps that were needed earlier but are no longer needed. Like I said, I will retire my guide as too confusing now.
Click to expand...
Click to collapse
I started out with the standard 3.2 on my Xoom Wifi
with a nagging system message to update (I am guessing 3.2.2)
So I followed thread 1249798 and now am unlocke & rooted!
I am also using Recovery: Eos Recovery R6
I still get the nagging system message to update.
I would like to load a custom ROM, probably Moray.
My questions are this:
1. Will the Nagging system update message cause a
problem loading a custom ROM?
2. I could use the process as described in thread 1249798
to load the ROM, but I have read that since I am rooted
I could use Quick Boot app. Is this true? What about the
ROM Manager app, could I use this to load Moray? What is
the difference?
3. Since my base is 3.2 I am guessing I cannot load any
EOS ICS Rom's, is this correct? I need to bring my base
to 4.0 right?
4. Both Hammerhead and Moray state that they are both:
"Pre rooted with su and Superuser". Does this mean I did
not have to root my Xoom, I could have just loaded either
of these Roms and become rooted?
5. I have read some comments about:
/system/etc/install-recovery.sh
If I remove this file, will this stop the nagging System Update message?
6. Do I need to back anything up prior to loading a ROM?
Thanks!
Still with that, you can flash TEAM EOS ROM ICS. just boot into recovery and flash the TEAM EOS ROM. Mine was 3.2.1 as well. GOOD LUCK
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 at https://dl.google.com/dl/android/aosp/nakasi-jwr66v-factory-d341d356.tgz
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4) Type
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-nakasi-jwr66v.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.3 and ready to send in your tablet for warranty purposes if you so desire.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
Also, thank you to XDA user Shano56 for the formatting help on this post.
chris.wueste said:
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
1) Make sure you have your ADB and Fastboot drivers installed and working.
2) Download the factory image for the Nexus 7 here
3) Unzip the factory image into the same directory as your Adb and Fastboot drivers.
4) Plug in your device. With the device on the home screen, type "ADB reboot bootloader" or if your device is off, press and hold both volume keys and press the power button. After holding all three buttons for a couple of seconds, your bootloader should launch.
5) This should reboot you into the bootloader. Now type "fastboot flash bootloader bootloader-grouper-3.34.img"
6) Next type "fastboot reboot-bootloader"
7) Now type "fastboot -w update image-nakasi-jrn84d.zip"
8) Optional: If you would like to relock your bootloader for warranty purposes, make sure you are in your bootloader screen again and type "fastboot oem lock"
9) I don't remember if the tablet automatically reboots at this point but if it doesn't just type "fastboot reboot"
That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
Click to expand...
Click to collapse
You should change the title to [Guide] How to return to Stock / Unbrick your Nexus 7
Helps out those getting bootloops or softbricks from geting root access in certain ways or messing with the build.prop
SladeNoctis said:
You should change the title to [Guide] How to return to Stock / Unbrick your Nexus 7
Helps out those getting bootloops or softbricks from geting root access in certain ways or messing with the build.prop
Click to expand...
Click to collapse
Not a bad idea. Done and done. Also, I have proofread it several times over to ensure it is correct but would you mind making sure that all of the commands were typed correctly. My eyes are going crosseyed over here.
Nice guide man, I changed the format a little to make it easier to read. Use it if you want, won't be offended if you don't.
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 here
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4) Type
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-nakasi-jrn84d.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes if you so desire.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
If you want to use it and are too lazy to quote my post - http://pastie.org/pastes/4279753/text
The commands look good to me however I've never used "fastboot -w update" so can't say for that
Shano56 said:
Nice guide man, I changed the format a little to make it easier to read. Use it if you want, won't be offended if you don't.
First of all, I am in no way responsible for anything you do to your tablet period.
I have seen a couple of people asking how to return the Nexus 7 to stock after it has been unlocked, rooted and so on, so I figured I would write a quick guide as its super easy to do. Also, please make sure you make a backup of anything you don't want to lose. This is important.
Before you begin, please make sure you have ADB and Fastboot drivers installed and working.
1) Download the factory image for the Nexus 7 here
2) Extract the factory image into the same directory as your ADB and Fastboot executibles (e.g. "\android-sdk\platform-tools")
3) Plug in your device. If you are booted into Android, open a command prompt to your ADB and Fastboot directory, then type
Code:
adb reboot bootloader
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
4) Type
Code:
fastboot flash bootloader bootloader-grouper-3.34.img
5) Next type
Code:
fastboot reboot-bootloader
6) Now type
Code:
fastboot -w update image-nakasi-jrn84d.zip
7) Optional: If you would like to relock your bootloader for warranty or security purpouses, make sure you are in your bootloader screen again and type
Code:
fastboot oem lock
8) If your tablet hasn't already rebooted automatically, type
Code:
fastboot reboot
That should do it. You should now be on stock Android 4.1 and ready to send in your tablet for warranty purposes if you so desire.
Additionally, here is an instructional video courtesy of XDA user SladeNoctis.
If you want to use it and are too lazy to quote my post - http://pastie.org/pastes/4279753/text
The commands look good to me however I've never used "fastboot -w update" so can't say for that
Click to expand...
Click to collapse
I updated the OP with your edits in it. Thanks for the help. I quoted you at the bottom
omg thank you so much. u saved my device
jarjar124 said:
omg thank you so much. u saved my device
Click to expand...
Click to collapse
Very welcome
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
chrisjm00 said:
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
Click to expand...
Click to collapse
In some cases due to the CWM not being official it cause bootloops by going to recovery in the bootloader.
SladeNoctis said:
In some cases due to the CWM not being official it cause bootloops by going to recovery in the bootloader.
Click to expand...
Click to collapse
There's a CWM official out?
Sent from my Nexus 7 using Tapatalk 2
chrisjm00 said:
Assuming you have a nandroid, can you boot into the bootloader, and simply ADB reboot recovery? Or does that bug prevent you from even doing that?
Click to expand...
Click to collapse
Assuming you have already flashed CWM, then the command would actually be fastboot reboot recovery. Not sure what but you speak of.
Shano56 said:
There's a CWM official out?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes. There sure is. If you have Rom Manager installed it can be flashed directly from there.
I dont think you can really hard brick this device anyways
I'm sitting here at the command prompt with it on "erasing userdata"
It's been a couple minutes and I'm freakin' out! How long is it supposed to take? Everything flashed correctly, if I start the device now will there be an issue?
EDIT: Nevermind, just rebooted from the bootloader in the tablet and it booted fine. I'll get the OTA to 4.1.1 and that should probably fix any outstanding little issues.
hard brick?
I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.
I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?
chris.wueste said:
If your device is powered off, press and hold both volume keys and the power button simultaneously. After holding all three buttons for a couple of seconds, your bootloader should launch. This should reboot you into the bootloader.
Click to expand...
Click to collapse
Pressing and holding the Volume down + Power buttons works just fine to launch the bootloader (at least for me).
No need to press (and force) the entire volume rocker button at all.
nugalonious said:
I am stuck at the Google logo with a padlock and I'm pretty sure I have a hard bricked tablet. fastboot doesn't see the tablet or my computer for that mater through dmesg.
I've rebooted it countless times with vol + and vol - pushed and any combo thereof. It will only turn off completely when the battery dies because holding down the power key for 10 secs just reboots it back to the Google logo in about 5 seconds. I guess at this point I'm just waiting for Google to give me a RMA for a refund and I'll move on unless someone has any other ideas?
Click to expand...
Click to collapse
Try and press and hold just the power button for 30 seconds or so to re-boot the tablet and you should be fine and it should boot up just fine. From fastboot you cannot go into cwm recovery because of a bug.
I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:
FAILED (remote: (FileWriteFailed))
Anyone seen that before or have any ideas to fix?
I tried wiping cache/factory reset from CMW but no joy.
Thanks. Worked for me. I did get worried when i got (data transfer failure (too many links)) error when trying to flash the bootloader.
Turns out it was the USB port. I switched the ports and all was well.
But I followed the commands in side the flash-all.sh file
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jrn84d.zip
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
yeahthatsme said:
I'm trying to return to stock but get this message in the window from the ADB command after flashing the stock ROM:
FAILED (remote: (FileWriteFailed))
Anyone seen that before or have any ideas to fix?
I tried wiping cache/factory reset from CMW but no joy.
Click to expand...
Click to collapse
Try the commands i posted above and see what happens
Nuts. I tried it on many USB ports and did your commands one by one. Ended up in the same spot. It happens when writing 'userdata'...
Hello,
again i need help I have unlocked the bootloader on my Xoom, the i have flashed TWRP and downloaded a Rom and the Gapps. I copied the gapps onto the device and followed instructions which came with the rom. I was instructed to wipe "system" too which i did.
Of course that deleted the downloaded rom and gapps too. Now i have TWRP and was excited to mount USB storage and just copy over again the rom and gapps but unfortunately there is no mount as USB option.
What and how is the smartest way to go about it? I wanted to sideload over ADB but the device is not found. I have really tried everythin in my knowledge, hope someone can help
cheers
Come on guys, really need help here. My kids are killing me for the damn thing
I have same problem.......it's an issue of twrp !
Have you tried a micro sd card? (copy the rom and gapps there from a pc then put it in the Xoom, etc...)
Worst case, you should be able to grab the stock images http://forum.xda-developers.com/wiki/Motorola_Xoom and fastboot flash the device back to stock.
Have the same problem
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
Stock flash doesnt require adb, just fastboot mode. You may need to still install a driver, but if you can boot into recovery then the xoom should also be able to boot into fastboot mode and be recognized by a pc. If the instructions on the link I gave arent enough, I will see if I cant find something tomorrow when I am on a pc.
Sent from my GT-N8013 using XDA Premium 4 mobile app
hbtwender said:
dosada, could you solve the problem?
airesch, I tried to mount sd card but it is impossible. How can I return to stock without ADB because computer is not recognized?
Click to expand...
Click to collapse
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Solved
airesch said:
NOTE: This WILL erase everything remaining on the device. In the case of the above, I don't know that you have much choice, just be forewarned.
Lord AIO toolkit has all the tools you need (look at the second post if you need the Windows driver.) Extract both the stock image zip and the toolkit (unless you have the sdk, in which case as long as you can find fastboot.exe you should be fine,) to somewhere convenient. Install the windows driver if you never have before and reboot your pc.
1. Boot your Xoom in fastboot mode: Power+Vol+ until it says: Starting Fastboot protocol support (you may need to tap the Vol+ instead of holding it the whole time, my Xoom has always been a bit picky about the buttons.)
2. Connect the usb to the pc
3. In a Command prompt window, go into the extracted version of the toolkit above (or if you have the sdk, just go to where you have fastboot.exe from it)
4. Run the following commands (replacing the files at the end with the full extract path from your stock image zip extract)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
"fastboot reboot" if you want to stay unlocked or "fastboot oem lock" if you want to re-lock and follow the prompts. The Xoom will get OTA updates even if it's unlocked, so there should be no reason to re-lock unless you need to send it in for service.
The driver isn't what I used to use, but it *should* work, and the instructions should be correct as far as I can remember. As long as you don't flash the wrong image to the wrong place/run out of power during flashing/disconnect during a flash then none of this should permanently damage the hardware and should get you a working device again. It's just that it's been so long since I have personally done any of this that I have forgotten more than I ever knew .
Click to expand...
Click to collapse
Hey airesch, thank you for your support. I couldn´t follow yours suggestion because my xoom was not recognizing the PC or MAC. However I discovered that my sdcard was broken. When I´ve tried a new one with ZIP files inside it works perfectcly and I could return to my old room doing flah in the recovery mode of TWRP2.2.
It is important to note that my Xoom did not find .IMG files inside the card but only ZIP ones. Any way it worked perfectly and I hope this solution will serve to other in solving his/her problems.
Many thanks
Well, that works too, and that was closer to what I originally suggested (tho I didn't expect you had a bad sd card.)
And yes, recoveries generally don't support IMG files directly, you need to have a specially crafted zip to flash those in. IMG files directly are for fastboot/pc tool flashing.
Congrats on fixing it.
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!