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.
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Hey bro, I've used these guys. Good luck
https://www.needrom.com
Sent from my HTC One M9 using Tapatalk
No RCA I might need to find a similar tablet and dump the firmware
kapicarules said:
No RCA I might need to find a similar tablet and dump the firmware
Click to expand...
Click to collapse
It's been a while since I played with RCA devices, which version of Android is it running?
NepoRood said:
It's been a while since I played with RCA devices, which version of Android is it running?
Click to expand...
Click to collapse
Android 6.0
kapicarules said:
Android 6.0
Click to expand...
Click to collapse
Sorry, not on the Chinese site we used for Viking and Maven firmware, it may show up eventually though...
link me to that chinese website
kapicarules said:
I got a rca voyager 3 model RCT6973W43 and I need to flash a new rom which I cannot find anywhere. Can you send me a ROM and the flash tool? I got it free and I want to try it get it working. It’s stuck at the voyager 3 logo
Click to expand...
Click to collapse
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
DMon04 said:
Bro,the device hasn't even been rooted yet. I just purchased one today. There is supposedly a bootloader unlock but no custom recovery yet and no root yet
Click to expand...
Click to collapse
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Getting anywhere on this?
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
BA_Flash_GOD said:
You get anywhere on dev for this device? I found one at work and was wanting to give it a shot.. unfortunately it's barren here and supa old hah.. AOSP would be nice for this though.
Click to expand...
Click to collapse
Unfortunately I did not. Mine is still a brick sitting on a shelf, been playing with GSI/Treble for oneplus 6 lately.
darkvoxels said:
I want to compile AOSP for it and not just root it. Have done it for my pixel but its easier with begin provided propitiatory blobs.
I found this other post on a similar device https://forum.xda-developers.com/general/general/guide-rca-voyager-rct6873w42-unlock-t3582973
Got into fastboot via usb debugging adb reboot fastboot (There doesn't appear to be a button shortcut to boot into it so you may be SOL even if a rom does come out)
Successfully Unlocked the bootloader
Was able to get a root shell via booting the cwm recovery
Dumped the boot.img, recovery.img via CWM but system failed
Was able to dump system via dd command
Still new to ROM building trying to understand vendor trees and device trees for building an AOSP ROM for it, noticed the system doesn't have a /device folder so a lot of tutorials don't seam too helpful.
Flashing the CWM recovery image from the above link breaks the recovery, had to flash back to old recovery, my next steps are to try and modify the stock recovery to enable adb so if i bork system i can button boot to recovery and use adb to get to fastboot otherwise it will be bricked...
Click to expand...
Click to collapse
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Isrgish said:
I realize this is an old post but I'm hoping you may be able to help me.
I just got this device and was wondering how you got the bootloader unlocked. When I try to select OEM unlock in settings it just jumps back to off. And fastboot flashing unlock gives me an error.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
darkvoxels said:
Hi yeah it's been a while since I bricked mine.. still sitting on a shelf as brick.. If I remember correctly when you do the OEM unlock from fastboot it flashes very briefly the screen to the unlock with instructions and button combination. What I did was run the command while using my phone to record the screen so see the instructions, then I went back watched the video to see what they were
I then went back to fastboot got the command ready again got my fingers in position before hitting enter and just tried to be as fast about it as possible and it worked for me.
Click to expand...
Click to collapse
Thanks for the reply.
How did you do a record the screen? Is there such an option while in fastboot?
Thank You,
darkvoxels said:
... using my phone to record the screen so see the instructions, then I went back watched the video to see what they were ...
Click to expand...
Click to collapse
Can you please tell me how you recorded the screen while in fastboot?
Thanks
I managed to get the bootloader unlocked on my Alco RCA Voyager III and just never got around to finding recovery or anything for it, this device a lost cause or am I just missing something? I don't think I can pull off making a recovery or rom yet but I can give it a shot if no one else is bothering with this device now a days.
@Trolldizzle How did you get it unlocked?
Thanks
@Isrgish I used fastboot flashing unlock command if I remember correctly, been a little bit since I did the unlock but I am like 90% sure that was the command.
i had get link here : findrom.info/rca-rct6973w43
you can try
Here you can find thr ROM. http://detonnot.com/3Xt3
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
BikerFry said:
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
Click to expand...
Click to collapse
Try flashing the stock boot img, it should but back stock recovery, you should be able to do it in fastboot too.
BikerFry said:
Help. I was so excited for my new phone that I made a n00b mistake - Booted into TWRP and flashed the TWRP zip to permanently install before I remembered to allow oem unlocking in the OS - Developer Setting. Now my phone won't boot because of the custom recovery, I can't flash anything because the bootloader is locked, and I can't get into the OS to allow unlocking.
The only thing I can do is fastboot boot twrp.
How do I fix this?
Click to expand...
Click to collapse
Follow steps here https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Sent from my OnePlus6 using XDA Labs
I can't flash anything. I get "Failed remote flashing is not allowed in lock state".
I can fastboot boot twrp so maybe could try flashing that way, but I can't get the phone to show up in windows explorer to transfer any files.
Wrong forum.
matze19999 said:
Wrong forum.
Click to expand...
Click to collapse
Sorry about that.
Might have just made a little progress. Learned the ADB Push command, loading an ota.zip and a boot image now. Hopefully can flash one or the other or both via twrp. Fingers crossed. Thanks either way guys.
tried Flash Image - boot image I had downloaded. It flashed successfully lol but I still can't boot the OS. And now I can't fastboot boot twrp either. ****. What have I done? lol. Come on it's android there has to be a way.
I appear to now be officially ****ed. Must have somehow been the wrong boot image, now I can't even boot into TWRP. I think I'm dead in the water. Can't flash anything, can't boot into TWRP. Any ideas? Will happily paypal a few bucks to anyone who can un**** me.
BikerFry said:
tried Flash Image - boot image I had downloaded. It flashed successfully lol but I still can't boot the OS. And now I can't fastboot boot twrp either. ****. What have I done? lol. Come on it's android there has to be a way.
I appear to now be officially ****ed. Must have somehow been the wrong boot image, now I can't even boot into TWRP. I think I'm dead in the water. Can't flash anything, can't boot into TWRP. Any ideas? Will happily paypal a few bucks to anyone who can un**** me.
Click to expand...
Click to collapse
have you tried the unbricking tool
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Will try it now. Thanks!
BikerFry said:
Will try it now. Thanks!
Click to expand...
Click to collapse
how are getting on with the unbrick tool ??
hallelujia the unbrick tool worked!!! So excited to be back making playing with the new toy! I was sure I was screwed, somehow didn't come across that tool in my googling. Thanks man. Imma kick a couple bucks your way with that donate button. Saved me from sending it back to oneplus and going a couple weeks without the new phone.
Now carefully...
BikerFry said:
hallelujia the unbrick tool worked!!! So excited to be back making playing with the new toy! I was sure I was screwed, somehow didn't come across that tool in my googling. Thanks man. Imma kick a couple bucks your way with that donate button. Saved me from sending it back to oneplus and going a couple weeks without the new phone.
Now carefully...
Click to expand...
Click to collapse
its fine my friend dont need the money just glad it helped ya :good::good::good::good:
Well thank you very much. I'm not too proud to freely admit I'm a happy kid with a new toy now. Thanks!
Disclaimers:
> I am NOT encouraging anyone to do this. I'm not responsible for anything that happens to your device once you've rooted it already. I did this out of curiosity and I'm just sharing my experience.
> Also yeah, Rmx2040. Not Rmx2040EU.
> It's doable, but it is NOT stable. It boots but you can't use the phone normally. You know, like how you'd normally use a phone.
> I SOFTBRICKED MY PHONE.
Bugs:
UI Restarts every time you go landscape and go back to portrait
Can't open camera
UI Restarts every time you scroll on playstore or anywhere with lots of images
Phone lags, actually no, it restarts all the damn time
NOTES:
@Kraitos was looking for boot.img files so i decided to do a little digging too. I saw in a post somewhere that you need vbmeta.img and a patched (via magisk) boot.img from the device itself.
The "vbmeta.img" I used here was from a Realme 5. I figured all they 'kinda' looked the same plus I don't know if the file is also patched. I tried patching it in magisk but it didn't work, so I just grabbed a (patched?) vbmeta.img (from Realme 5 somewhere in the internet) and used that for our device which is, Rmx2040 (6i)
I grabbed the boot.img from the official ozip file in realme's site (From version A.27, I couldn't find any boot.img for A.31 because they haven't updated the link in the site yet). I opened it up, looked for it, grabbed it and patched it using magisk. Thankfully, it worked.
I used both the vbmeta.img (again, idk if it's patched) and the patched boot.img to root my device. I doubted it too, I thought it'll give me a bootloop or something, but it didn't.
If you want to do it, here are the steps:
Unlock your bootloader. Go here:
https://forum.xda-developers.com/realme-6i/how-to/unlocking-bootloader-realme-6i-rmx-2040-t4174255
Credits to @Kraitos for this awesome guide on how to unlock Rmx2040's bootloader.
If you're done unlocking your bootloader, download these files:
boot.img:
https://drive.google.com/file/d/1D7S9JGwDusyL6hJ6pWrFRBLo_9DdQLGR/view?usp=sharing
vbmeta.img:
https://drive.google.com/file/d/1Do2SfGI_Tp2jERcO77Vh1vEfjiQ6Xxe9/view?usp=sharing
Portable adb fastboot (if you don't have it yet):
https://drive.google.com/file/d/1m78UIsabMQlCvNIIv2e4xI19pN9b1otw/view?usp=sharing
Put all in one folder, it doesn't have to have a name.
Extract the zip file (minimal_adb_fastboot_1.4.3_portable.zip)
*Your folders should have the ff:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
boot.img
cmd-here.exe
Disclaimer.txt
fastboot.exe
vbmeta.img
Enable USB debugging in your phone.
Connect your phone to your pc.
Double click "cmd-here.exe"
Type the following in CMD:
adb reboot bootloader
If it displays a text in the middle, type "fastboot devices" on cmd. You SHOULD your phone's code there. If it doesn't display anything, replug the type C cable on your phone and type it again, do this until it shows.
Copy this and paste it in CMD:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Then press enter.
once it's done, copy this next:
fastboot flash boot boot.img
Then press enter.
Reboot your device by typing this in CMD:
fastboot reboot
If you've made it this far, you should install the latest Magisk Manager after you've unlocked the bootloader though. Or do it last, whatever you prefer works.
Viola, now you have an unstable phone.
I'm gonna try locking my bootloader later to flash the A.27 ozip later, I hope going back to "stock and unrooted" fixes the bugs I've experienced :|
I don't really know anything besides trying stuff out, I just wanted to see if it'll work properly with root. If anyone here noticed that I've done something wrong, please do tell me. I wanna try all the methods we can think of just so we can root this device.
Have a wonderful day y'all
Edit:
Everything went bad. I locked the bootloader because I needed access to stock recovery. It gave me a "red state"
I don't know how to fix this problem :|
Awesome guide and thanks for mention you know some people do that if you pay them to unlock bootloader and rooting device so this thread will be a savior to alot of people , I'll do testing in a couple of days asap i get a laptop relocking bootloader is mostly the same when you unlocked bootloader so it should be easy to flash stock again
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Joesh.lucas said:
Alright, so, quick update:
I tried to lock the bootloader while it had root (in my case, magisk). When I did, the phone went to "red state" (For those who don't know, it's basically bootloop wherein the phone never goes to recovery no matter what you do. Not even in stock).
Now, my phone is broken. It bootloops. I don't know what to do with this problem except going to a service center and have this fixed. Does anyone know how much it costs for reflashing stock rom to realme devices?
Sidenote: I tried the volume + down/up method to get into fastboot mode or stock recovery, but it never works. And honestly speaking, I don't think it will. To get into fastboot mode the bootloader needs to be unlocked, so that's crossed out AND I can't get into stock recovery because the phone restarts every 5 seconds because of that pesky "red state" thingy at the start.
Click to expand...
Click to collapse
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
mehdi.shah said:
The problems you faced after rooting the phone is because you flashed an older version of boot.img thats why it wasn't working with latest rom and caused instability in system... And the second problem that you faced that red state thing..!! it was your fault you shouldn't relocked the bootloader with a patched boot img.. and if you wanted to boot the stock recovery you should have used the command " fastboot reboot recovery " this command in fastboot mode reboots the phone to recovery mode... Well i want to know what happend did your phone survived??
Click to expand...
Click to collapse
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Joesh.lucas said:
Thanks for the information, I now understand that I should use the same boot.img. It was worth the experiment tho, I just hoped I did it better so I wouldn't have to go through this process again.
My phone is here with me. It's still stuck on red state and I haven't went to a service center to have it fixed yet. I went to Hovatek to look for some ways to fix this problem. I tried using miracle box and the SP flashtool method but the latter had problems with the scatter file and the former didn't get past this:
Waiting for USB Port...
Set OPPO PreLoader USB VCOM (Android) (COM4)
>>Please Hold "ON" to connect with the phone...
I also looked a little bit more into it and I found out that I can use the OFP file and the flasher application here: https://firmwarex.net/realme-6i-rmx2040-official-firmware/
But unfortunately, I can't use the application because it's asking for an OPPO ID or something. Either I bring this phone to a service center or I'll just let it be this way until I decide to sell it somewhere. I hope I'll be able to fix this on my own tho, at least, someday.
Edit:
You can read more of my experience here:
Rmx2040 (realme 6i) scatter file
Hi guys, I'm trying to get the scatter file in this and so far I found this on the ozip file: preloader 0x0 pgpt 0x0 recovery_a 0x8000 misc 0x2008000 para 0x2088000 opporeserve1 0x2108000 opporeserve2
forum.hovatek.com
I'm subma rine13.
Click to expand...
Click to collapse
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Joesh.lucas said:
Woah, is it true you've rooted it? How did you manage to pull it off? Is it similar to what I did except with different files?
Oh and yeah, I think I'll need to bring this to an authorized service center to have it fixed. In your currency, how much do you think it costs to flash the stock rom back to the phone? This has been a question that's been bothering me for months. I do hope it isn't pricey, because if it is then maybe I'll never have it fixed.
Click to expand...
Click to collapse
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
mehdi.shah said:
Yeah the procedure was the same as yours... I unlocked the bootloader i was on A27 build... And i downloaded the latest ozip file from the official site and i opened it up in file manager it asked if i want to update the software i clicked yes.. and it rebooted to stock recovery and started updating the device.. after successful update i opend up the ozip file by renaming it to .zip and extracted the boot.img and vbmeta.img. i patched the boot.img with latest magisk manager and tha than flashed those files in fastboot mode... With same commands that u used... And everything went well and its all good and rooted no problem at all..
And yeah the service center thing.. if its the software issue than the charge around 1.5 to 2k rupees in my country...which is around 9.34 to12.4 US dollars..
Click to expand...
Click to collapse
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
sqzd0 said:
Does root work as it should?
Russian community guys reported that root exists in the system but not works at all. Rooting procedure looks the same.
Click to expand...
Click to collapse
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
I don't mean to be rude but, can you make a thread for that? Some rmx 2040 owners want to root their device and I think i just gave them a recipe for disaster.
Oh and by the way, thanks for answering my question. I have another one, will it be okay to update your device whilst rooted? If so then how do you stop the auto update?
(Sorry for the questions man hahahaha I wanted the same outcome but I failed miserably :| )
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro give me boot.img a37
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Give me boot.img of a37 version
mehdi.shah said:
Hey buddy i just rooted my realme 6i (RMX 2040) on build number A.37... everything went smooth and working flawlessly.... No system instabilities at all... Btw sorry to hear that your phone is still in brick state.. actually thing is oppo does not allow the users to flash stock rom on locked bl devices that why flasher tool asks for oppo authorized account in order to flash the device... And about SP flash tool.. it will not work either we have to wait for the patched rom that can be flashed on locked devices with sp flash tool
Click to expand...
Click to collapse
If you rooted dump the stock recovery and boot.img through terminal emulator I will try to port twrp
Boot.img and Vbmeta file can now be accessed by clicking the text above
Do is still need to relock my bootloader inorder to downgrade to A.27 update ? Thanks
mehdi.shah said:
Yeah it is working like it should work... I tried many things... Different magisk modules.. even changed boot animation with root file manager every thing works like charm..
Click to expand...
Click to collapse
Bro i tried the rooting process and i didnt check the boot and i rooted my phone the wifi,blueooth, camera, etc doesnt work anymore. If POSSIBLE can i revert it back to normal?
Can anyone provide me a twrp recovery file for realme 6i rmx2040 A.47 plsss
[READ FIRST] {BLU G90 PRO} I am new to all this, I started learning about rooting a week ago. If you can help, please explain in detail. TL/DR at bottom
[CAUSE] I'm not sure but I attempted root by useing migisk and lateset firmware boot.img provided by xda.
[PROBLEM] My phone constantly bootloops. I cannot access recovery mode as it just reboots. adb won't work as the phone does not connect to the computer. I can go to fastboot mode though.
[ATTEMPTS] I have let the battery die which did nothing, I tried to let the phone charge but it does not go up that much, but fastboot mode at least lets it chare a little. I have tried to reflash the stock boot.img but adb doesn't work. (see video).
[RESOURCES] I have all files assosiated with this. I now have stock firmware as well. Willing to wipe phone completely. I am bootloaded.
TL/DR: ****ed up root with wrong boot.img in magisk. Bootlooped and low battery..
[VIDEO]
I_like_root_pls said:
[READ FIRST] {BLU G90 PRO} I am new to all this, I started learning about rooting a week ago. If you can help, please explain in detail. TL/DR at bottom
[CAUSE] I'm not sure but I attempted root by useing migisk and lateset firmware boot.img provided by xda.
[PROBLEM] My phone constantly bootloops. I cannot access recovery mode as it just reboots. adb won't work as the phone does not connect to the computer. I can go to fastboot mode though.
[ATTEMPTS] I have let the battery die which did nothing, I tried to let the phone charge but it does not go up that much, but fastboot mode at least lets it chare a little. I have tried to reflash the stock boot.img but adb doesn't work. (see video).
[RESOURCES] I have all files assosiated with this. I now have stock firmware as well. Willing to wipe phone completely. I am bootloaded.
TL/DR: ****ed up root with wrong boot.img in magisk. Bootlooped and low battery..
Click to expand...
Click to collapse
How to root/alternate for twrp? BLU G90 PRO
I have spent 2 days trying to figure out how to root my g90 pro. I can't find twerp for it and every possible guide I find destroys my sanity when I find out it won't work. I have magisk as a zip file on my phone right now, is there an alternate...
forum.xda-developers.com
[CAUSE] You not know how using fastboot mode:
Code:
fastboot devices
If okay so you can using:
Code:
fastboot flash boot boot.img
But the boot.img file is in the folder platform?
[PROBLEM] You need better file patched. Maybe your pacthed_boot.img is wrong! So you can flash TWRP but need modified vbmeta file. I can help with that file!
[ATTEMPTS] two ways: 1- charge battery for using with fastboot. 2- Using SPFT for flash stock ROM or stock boot.img only.
[RESOURCES] You know use SPFT for flashing stock ROM?!
Created 2 posts with same device?? daaammm
Look this guy!: https://forum.xda-developers.com/t/...310ww-mt6765-android-10.4163497/post-84082633
LMFAO I FORGOT THE ./
but your post also made alot of things click for me. I was feeling down cause I though I ****ed up my first phone before a week even passed. Thanks for the help! Feeling alot better now!
also I got the recovery mode to pop up and I'm downloading verified stock firmware rn. Will update
Everything is fixed! I used spft and installed the stock rom! Everything is backing up now from my cloud account.
Now I want to root even more and I got a bit more experience. I saw your post mentioned a program bprd. Should I use that instead of the twrp build I found for this?
Also thanks!
I_like_root_pls said:
program bprd
Click to expand...
Click to collapse
Where did I write that?
Now understand: You have 2 ways for flash only recovery.img(TWRP or PBRP).
Using SPFT;
Using adb-fastboot.
Obviously if you want ROOT without Custom Recovery you should use magisk to create patched_boot.img and flash with 2 same ways.