Develop Bugs

[Q] Can't root my HTC Wildfire

For days now I have been trying to root this HTC Wildfire (NOT Wildfire S) that my dad gave to me (so I take it that this phone is very old), because I need to install Android 2.3 on it to be able to download Skype (the phone is stuck on Android 2.2). However after trying many guides, on this website AND others, I am simply unable to do it, so that is why I am writing this forum post.
This is the HBOOT screen:
(As a new user I can not post any images or links for some reason so I just typed this
*** LOCKED (OOW) ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Dec 13 2011, 12:08:54
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.

NurusS said:
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.
Click to expand...
Click to collapse
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk

heavy_metal_man said:
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.

NurusS said:
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.
Click to expand...
Click to collapse
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal

heavy_metal_man said:
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal
Click to expand...
Click to collapse
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?

NurusS said:
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?
Click to expand...
Click to collapse
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?

heavy_metal_man said:
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?
Click to expand...
Click to collapse
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?

NurusS said:
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?
Click to expand...
Click to collapse
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk

heavy_metal_man said:
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did what you said, I got <waiting for device> again.

NurusS said:
I did what you said, I got again.
Click to expand...
Click to collapse
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.

heavy_metal_man said:
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.
Click to expand...
Click to collapse
Fastboot is highlighted in red.

NurusS said:
Fastboot is highlighted in red.
Click to expand...
Click to collapse
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.

heavy_metal_man said:
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.
Click to expand...
Click to collapse
Once again, I just get <waiting for device>

NurusS said:
Once again, I just get <waiting for device>
Click to expand...
Click to collapse
Okay, then your issue is with your fastboot driver. Do you have another computer you can use?

Just install android SDK and jdk and then try to install your drivers as heavy metal man said. I hope this could work..or try to use this
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my Moto G using XDA Free mobile app

[Guide] Unlock Bootlader, TWRP and Root your Huawei MediaPad M2 8 - 10

As usual with this stuff. You do everything at your own risk. I am not responsible in any way for what you manage to achieve, either good or bad.
EVERYTHING IS ON YOU!
So. To unlock Bootlader, add Custom Recovery TWRP and root we need to do a little preparation. First of, It will cost you €4 to unlock the bootloader in this way, but given that your warranty is absolutely immaculate, it's worth every penny. You CAN get the code for free from huawei but at the same voiding your warranty.
Step 1.
We start with activating "Developer Options".
We do this by going to Settings -> About Tablet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2.
Then you click on Build Number 5 times.
Step 3.
When you have enabled the Developer Options, go to Settings -> Developer Options.
Step 4.
Once there, you should look up "Enable OEM Unlock" and select it. It will ask again if you are sure. Press yes.
Step 5.
After this, we need to change the USB port to something called "Manufacture Mode" which you do by opening the calculator (Huawei's own) in landscape mode
then type exactly this: () () 2846579 () () =
After pressing the = sign, then a hidden menu will show up. Do not mess around in here if you do not know what you're doing ...
Step 6.
Now you enter the "Background Settings" -> USB Port Settings -> Manufacture Mode and select "Manufacture Mode".
Select and close the menu. Back out to Home.
Step 7.
Now you must get HiSuite available here: http://consumer.huawei.com/minisite/HiSuite_en/
This is for you to get the right drivers. Just install and start up.
Step 8.
Connect the MediaPad to your computer with the USB cable. The MediaPad will ask if it's ok with USB debug. Take the "Always Allow" and ok.
Step 9.
Check in your PC Control Panel -> Device Manager so that it looks something like this.
Step 10.
Now let's get us a program called DC-Unlocker client. What it can do is unlock your SIM and get your Bootloader Unlock code that is unique to your MediaPad. This code can also be ordered from Huawei but then you can kiss your warranty
bye-bye. You will have to pay 4 Credits (€ 4) for the bootloader code. To unlock the SIM, it will cost an additional 4 credits. It costs 2 credits to relock the bootloader if needed for warranty issues.
Download DC-unlocker client here: https://www.dc-unlocker.com/downloads/get/B4oUVw8X
Take the opportunity to make a user as well as buy credits here: https://www.dc-unlocker.com/buy
Select New User and enter your desired username and email address. Once you have paid for your credits you will receive the password to your user via email and / or directly after managed payments (PayPal).
Step 11.
Start the DC-unlocker client as an administrator (Right-click DC unlocker2client.exe and select "run as administrator")
Step 12.
Now, change the Select manufacturer to "Huawei Phones". Leave the Select model on Auto Detect. Now press the magnifying glass.
Step 13.
Now it will look like this when the program has found the Mediapad.
Step 14.
Now, open the Server tab and enter your username and password you provided when you created your account. Then press the Check login to see how many credits you have.
Step 15.
Now open Unlocking tab and select the "Read bootloader code" (This will cost 4 credits)
Step 16.
Now your code is shown at the selected area. Print / Save it down somewhere safe because that code is unique to your MediaPad and it will cost you 4 credits to get it again.
Step 17.
Now that you have your bootloader code, we need to restore the MediaPad to HiSuite mode again instead of Manufacture mode. You do this by redoing the step with the hidden menu with the calculator at Step 5. Go to the same page but select HiSuite instead of Manufacture Fashion.
Step 18.
Now that we have Bootloader code, we have to arrange ADB and Fastboot to send some commands to the MediaPad.
ADB and Fastboot I have collected here: https://mega.nz/#!ck8CDJra!XsExtdNcwGX7zMW9F6uYo155YuMd71lV7G9vXIYrhe8
In that folder I also have TWRP (twrp.img) for MediaPad M2 and a theme that changes the language to English (ui.zip) as TWRP is in Chinese.
Unzip the folder in your root (c:/) or wherever you want.
Now open the command prompt (the Administrator) in the computer and navigate to the folder so it looks something like this.
Step 19.
Start the MediaPad in fastboot / Recovery mode. This is done by turning off the MediaPad. Inserting the USB cable from the device to the computer while the MediaPad is off and quickly pressing the Power button + volume down button until this image appears.
Step 20.
We start by unlocking the bootloader, type: fastboot oem unlock your-boot-unlock-code (So: fastboot oem unlock 8794898763874)
Now you have unlocked your bootlader. Now type: fastboot reboot
The MediaPad will reboot.
Step 21.
Turn off the MediaPad and repeat Step 19.
When you are in fastboot / Recovery mode, enter the command prompt: fastboot flash recovery twrp.img
Now you have flashed TWRP Recovery.
At the command prompt, type: fastboot reboot
The MediaPad will reboot.
Step 22.
Now, connect your MediaPad to your computer and navigate to the internal memory. You will find a folder called TWRP.
In this folder, create a new folder and name it "theme". In this folder, copy ui.zip from my adb folder.
You can also take the opportunity to copy the BETA-SuperSU-v2.67-20160121175247.zip to your MediaPad (suggested internal memory root or download folder or wherever you want as long as you know where you have it).
Step 23
Now we open the command prompt again and type: adb reboot recovery
Your MediaPad will reboot and suddenly you are inside the TWRP Recovery.
Optional: You can also enter recovery by booting the tablet by pressing power button + volume up. Keep holding volume up until you enter TWRP
I recommend that you make a TWRP backup of your MediaPad BEFORE rooting... Just incase
Step 24
Install BETA-SuperSU-v2.67-20160121175247.zip and you have ROOT.
Now you are ready!
Install an app that allows you to reboot to recovery easy for example "Quick Boot" in PlayStore.
Do you have any any questions, just ask them here!
----------------------------------------------------------------------------------------------------------------------------------------------
BIG THANKS TO A LOT OF PPL. If you feel left out or forgotten, send me a message and i will pay the proper respect.

wait...what is the key to that file with ADB and Fastboot please?

warcraftan said:
wait...what is the key to that file with ADB and Fastboot please?
Click to expand...
Click to collapse
Bah. Really sorry about that! Here it is.
https://mega.nz/#!ck8CDJra!XsExtdNcwGX7zMW9F6uYo155YuMd71lV7G9vXIYrhe8
Sent from my Nexus 6P using Tapatalk

somehow i can not flash twrp.img file. My tablet is completely unlocked, but in the command prompt i can not flash twrp...the window of command prompt says that flashing is "Okay" then i type flashboot reboot and in there is nothing called "twrp" folder...
Any help?
Thanks a lot!

warcraftan said:
somehow i can not flash twrp.img file. My tablet is completely unlocked, but in the command prompt i can not flash twrp...the window of command prompt says that flashing is "Okay" then i type flashboot reboot and in there is nothing called "twrp" folder...
Any help?
Thanks a lot!
Click to expand...
Click to collapse
IF it says OK you have successfully flashed TWRP.
And the TWRP folder won't appear until you have booted in to recovery at least once. The thing is that it will be in Chinese unless you do the step before booting in to recovery.
Therefore you create a folder in sdcard/ called TWRP and in that folder another folder that you call theme there you add the ui.zip.
So complete address is /sdcard/TWRP/theme
(Note, big letters on TWRP)
Sent from my Nexus 6P using Tapatalk

i have created folder called "TWRP" by myself, then i have created "theme", copied that ui.zip and? nothing changed..
IF i reboot device once again to recovery=>default screen with fastboot will appear. I even tried to download an app from store called "quick boot", downloaded=>choosed to reboot into the recovery and app stopped working (because it was saying that i dont have root)

warcraftan said:
i have created folder called "TWRP" by myself, then i have created "theme", copied that ui.zip and? nothing changed..
IF i reboot device once again to recovery=>default screen with fastboot will appear. I even tried to download an app from store called "quick boot", downloaded=>choosed to reboot into the recovery and app stopped working (because it was saying that i dont have root)
Click to expand...
Click to collapse
You have to use the right command:
adb reboot recovery
You can also enter recovery by booting the tablet by pressing power + volume up. Keep holding volume up until you are in TWRP.
Sent from my Nexus 6P using Tapatalk

Still can not boot into the recovery. I would like to inform you, that i do own 8.0 MediaPad M2 Pro version (which comes with 3GB of RAM) (cos i saw you have 10.1)

Reb0rn said:
You can also enter recovery by booting the tablet by pressing power + volume up. Keep holding volume up until you are in TWRP.
Click to expand...
Click to collapse
Ahh, i see, finally i got this! omg, thank you a lot, much appreciate your help. now it works everything fine, now i will root my tablet

warcraftan said:
Ahh, i see, finally i got this! omg, thank you a lot, much appreciate your help. now it works everything fine, now i will root my tablet
Click to expand...
Click to collapse
Don't forget the thanks button

I did not you deserved it.
And one more thing to all: in other thread one guy was talking about not working xmod (xmodgames properly) even if you have your device rooted (by this method). After like 10min i finally has launched even xmod (because most of all you need for this really true method of root), i had some issues with installing etc. but now i can play my CoC with that
hopefully you wont take it as a spam, take care. bb

warcraftan said:
I did not you deserved it.
And one more thing to all: in other thread one guy was talking about not working xmod (xmodgames properly) even if you have your device rooted (by this method). After like 10min i finally has launched even xmod (because most of all you need for this really true method of root), i had some issues with installing etc. but now i can play my CoC with that
hopefully you wont take it as a spam, take care. bb
Click to expand...
Click to collapse
Apparently KingRoot doesn't root the right way.
This works 100%.
Sent from my Nexus 6P using Tapatalk

@Reb0rn:
I have a Huawei M2 8.0 and don't have the "Enable OEM Unlock" option in the Developer Options
Any ideas how to proceed further?
EDIT: Nvm, I proceeded with the rest of the guide and it worked fine.. I didn't have to enable OEM Unlocking.
BTW, your TWRP link on Mega is broken - it's asking for a decrypt key. Luckily I found a different TWRP somewhere else and that appears to be working fine.

[deXter] said:
@Reb0rn:
I have a Huawei M2 8.0 and don't have the "Enable OEM Unlock" option in the Developer Options
Any ideas how to proceed further?
EDIT: Nvm, I proceeded with the rest of the guide and it worked fine.. I didn't have to enable OEM Unlocking.
BTW, your TWRP link on Mega is broken - it's asking for a decrypt key. Luckily I found a different TWRP somewhere else and that appears to be working fine.
Click to expand...
Click to collapse
Gonna fix it during the day
Edit. Fixed. https://mega.nz/#!ck8CDJra!XsExtdNcwGX7zMW9F6uYo155YuMd71lV7G9vXIYrhe8
Sent from my Nexus 6P using Tapatalk

Thanks for the info!
I'm looking for the HUAWEI M2 A01L 10" 3GB, 16GB, LTE,
Is it possible to install a dialer app after rooting to make phonecalls?

zedoc said:
Thanks for the info!
I'm looking for the HUAWEI M2 A01L 10" 3GB, 16GB, LTE,
Is it possible to install a dialer app after rooting to make phonecalls?
Click to expand...
Click to collapse
It's already there stock dialer. Don't you have it?
Sent from my Nexus 6P using Tapatalk

Reb0rn said:
It's already there stock dialer. Don't you have it?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Ok good to know thank you, i didn't buy it yet but i think i'll go for it

Stock recovery
Can you please upload stock recovery? THX.

matata86 said:
Can you please upload stock recovery? THX.
Click to expand...
Click to collapse
Hmm... Not likely. Maybe extract it from a rom update IF there is One.
Sent from my Nexus 6P using Tapatalk

hmmm .. exist flashable zip stock rom?

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying:

Help I bricked my Oneplus 3

Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))

have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.

bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)

Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs

bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?

Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"

Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?

ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol

bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?

gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs

Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something

simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))

Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?

Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..

jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...

simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english

Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.

can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!

How To Guide [ROOT] [FLASH STOCK]

DISCLAIMER:
Please post failures and successes. Keep it relevant, everything else to the DMs please. It makes it easier for others to Q&A. Everyone thanks you for your understanding.
***IF YOU ARE NEW BEWARE!!! BEFORE YOU CHANGE ANYTHING MAKE A BACKUP. LET THIS APPLY TO EVERYTHING. WHENEVER THE OPTION TO BACKUP IS AVAILABLE IT WOULD BE WISE TO DO SO. FAILURE TO BACKUP YOUR DEVICE WILL RESULT IN LOSS OF DATA***
ALL LINKS ALLOWED, APPROVED AND/OR UTILIZED BY XDA. SPECIAL THANKS TO ALL THE DEVS WHO CREATED THE TOOLS WITHOUT WHICH THIS WOULD NOT BE POSSIBLE. I DIDN'T BUILD ANY SOFTWARE MENTIONED IN THIS POST. IF YOU BRICK YOUR PHONE, DO NOT BLAME ME. I'M NOT TELLING YOU HOW TO DO IT, BUT NARRATING A GUIDE TO HOW I DID IT. YOU HAVE BEEN WARNED
REVVL V+ 5G TMOBILE VARIANT ANDROID 11
IT SHOULD BE NOTED THAT SOME PEOPLE ARE REPORTING LOSING WIFI AFTER ROOT, AS HAVE I. I HAVE NOT YET FIGURED OUT HOW TO FIX THIS. I'M THANKFUL FOR ANY ASSISTANCE. FLASHED STOCK BOOT_A DIDN'T FIX IT, ONLY FLASHING BACK TO STOCK ROM. ON ANOTHER IDENTICAL PHONE DIDN'T LOSE WIFI. YOUR GUESS IS AS GOOD AS MINE. LOOKING INTO IT, NO PROMISES
Without further ado, let's start at the unboxing.
1) PREP PHONE:
power on. navigate to settings>about phone and tap "build number" seven times to enable developer options.
navigate to settings>system>developer options and enable "USB Debugging" and "OEM unlock"
FIRST disconnect the device from your comp THEN power the device off.
2) DONWLOAD PYTHON & DRIVERS:
Python
BE SURE TO TICK THE BOX THAT SAYS ADD PYTHON TO PATH and install.
Download and install mediatek drivers from here:
Mediatek USB drivers
Download and install UsbDk from here:
UsbDk
Download MTK client from here:
MTK client
and extract to the desktop. Open the folder and move everything to
C:>Users>[username]>AppData>Local>Programs>Python>Python310
In the 310 directory press Alt + D to highlight your directory path and type CMD and hit enter. This opens a command prompt in the Python310 directory.
In cmd type this command without "":
"python setup.py install"
Go make a sandwich. Preferably turkey with mustard.
When you finish your sandwich, come back and type this command without "":
"python -m pip install -r requirements.txt"
Do not exit the command window.
3) BOOT INTO B ROM MODE:
This is kind of tricky when you don't know it. The screen will will be black. Sometimes, the device will not even vibrate. There's no sunbathing android, no "No Command", no fastboot, no download mode, no recovery- nothing, nada, zip, zilch, goose egg.
Make sure you unplug the device entirely from charger and pc BEFORE you power off. Now that you properly powered off, hold ONLY BOTH volume + - keys while you connect it to your PC. Try to be quick about it. DO NOT TOUCH THE POWER KEY. Continue to hold the volume keys until you know your device connected. When you hear your device connected jingle immediately let go. The screen will remain blacked out and unresponsive. It's normal.
Let's make sure we did it right. Enter the following command without ":
"python mtk e metadata,userdata,md_udc"
Disconnect and power on. If the device has been reset, then you have confirmation.
4) PREP PHONE AGAIN (STEP 1):
5) UNLOCK BOOTLOADER:
Enter the following command without ":
"python mtk da seccfg unlock"
~To relock the bootloader in the future use command "python mtk da seccfg lock". If you flash a custom recovery/ROM and want to return to stock, then you must unroot with magisk first, then flash stock ROM with SP flash tool at the end of this post~
Power on. On the splash screen you will see system type:
"Orange State
Your device is corrupted. Device has been unlocked and cannot be trusted. Press Power key to boot.
Will Reboot in 5 seconds."
This will happen each time you boot the device because your bootloader is now unlocked.
6) PREP PHONE AGAIN (STEP 1):
7) ENABLE ADB FASTBOOT COMMANDS:
Download sdk platform tools here:
sdk platform tools
Extract.
Navigate to the platform tools folder and type Alt+D to highlight directory and type CMD to open a cmd window in platform tools.
Connect device to pc and choose file transfer.
Enter the following command without ":
"adb devices"
A prompt will appear on your phone, click allow.
Enter the following command (again) without ":
"adb devices"
First you'll see a random, arbitrary number. Second time you should see your device serial number and "Authorized", "Allowed", or "Device".
Keep this cmd window open.
8) DOWNLOAD MAGISK AND PATCH BOOT IMG:
Download Magisk from here:
Magisk
Move it to your phone and install. You'll need to allow the installation from unknown sources.
Download firmware from here:
T-Mobile_REVVL_V%252B_5G.zip
Unzip and move boot_a to the downloads folder on your phone.
On your phone, open Magisk and click install and choose boot_a.
Make sure magisk_patched file is in your phone's download folder.
In your platform tools cmd window enter the following command without ":
"adb pull /sdcard/Download/magisk_patched_[numbers].img"
9) ENTER FASTBOOT MODE:
Disconnect device and power off. Hold Vol - and power to enter fastboot mode.
Connect device to PC.
10) ACHIEVE ROOT:
***NOTE: IN THIS STEP YOU MUST LOCATE THE PATCHED FILE ON YOUR PC AND COPY AS PATH. PASTE IT IN THE CMD WINDOW IN PLACE OF "[path to patched file]"***
In the platform tools cmd window enter the following command without ":
"fastboot flash boot [path to patched file]"
Now that you've achieved root, you can play around a little bit. But be careful what you go deleting if you get debloat happy like me and delete your NVRAM & wifi. Just in case you do, here's how to return to stock.
NVRAM backup. This video makes it look easy as pie. (It IS easy)
NVRAM Backup Tutorial
Now we have to bypass DA else SP flash tool will not be able to flash ROM.
Open cmd window and type the following without "":
"python -m pip install pyusb pyserial json5"
Then, update by entering the following command without "":
"python.exe -m pip install --upgrade pip"
Download LIBUSB:
LIBUSB
Run LIBUSB Win 32 filter installer and select Mediatek driver
Enter B ROM mode and connect to PC
Navigate to bypass tool and open "brom.bat"
Close cmd...
Run "flash_tool.exe" in sp flash folder
Options>options>connection tick UART
That's it. Now you can flash with sp flash without encountering error
Here is a helpful link that came from a senior mod:
mtk tool
Download SP Flash tool here:
SP Flash
Extract and launch flash_tool application
Download scatter mt6833 here:
MT6833_scatter.txt
Download bypass tool from here:
bypass tool
download rom2box:
rom2box
Download OTA and use a payload dumper to extract boot and scatter. You can also get DA, but it does nothing. You must bypass DA in order to flash ROM.
OTA
THIS SECTION IS FOR LATER REFERENCING, DISREGARD ANYTHING BELOW THIS
[A13 ota news https://www.t-mobile.com/support/devices/software-updates/t-mobile-revvl-v-plus-android-update]
[Twrp https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/?_ga=2.195721068.1777813512.1675477697-1767133243.1662515191]
~fastboot set_active other
~fastboot flash recovery_a twrp file
~fastboot flash recovery_b twrp file
[Sprout https://dl.twrp.me/sprout/]
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
https://www.mediafire.com/download/sxq4cz8bddmr49
https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file
https://download1526.mediafire.com/ih0pus48i1kg/mwl6h20noutg005/revvplus.zip
[Patched boot_a pending verification https://forum.xda-developers.com/attachments/magisk_patched-25100_hiu69-img.5648347/]
[FLASH STOCK MODEM FILE]
My next guide will be how to use assurance wireless with ANY phone. I'm using assurance wireless on my Oneplus N200 (DE2118).

Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!

smuskat said:
Hi. I read many posts of yours regarding the REVVL V+ 5G, I was encouraged by your progress, and took comfort that someone else had some of the same struggles that I did. I was able to unlock the bootloader, I was able to root the phone (using an img file posted by someone else here; I hadn't yet read your root recipe), but I was no longer able to connect to wifi. (is this familiar?) In trying to undo the mess, I ended up making my phone unbootable.
I wanted to install stock ROM from scratch. I read your instructions, but there's no scatter file in the ROM that you posted. So I'm confused.
I figured that I could install the stock ROM zip via TWRP; I googled and found a TWRP for "Sprout" (the codename of our device), but for the life of me I couldn't install it on my phone, no matter what I tried.
You're ahead of me here; perhaps you can get me on track. Right now, my phone isn't booting at all.
Thank you!
Click to expand...
Click to collapse
Hey, I finished the guide. You can return to stock following the guide above. As you may have noticed I edited this message instead of posting again. It's okay, cause I brought good news, right? Cheers

R41N MuTT said:
i totally forgot, yeah, i will look up the proper method to install twrp. it's supposed to be easy. i thought i was going to have to port twrp-and i still might- so i'm looking into it. i need to flash twrp myself. there is supposed to be a way to use rom2box or spflash or twrp or something to make a flashable zip. i don't know if that's a thing. it seems to me somebody needs to build a preinstaller that automatically flashes each img. for you. like a 1 click. if we can get twrp on this, that's the next step. to make a flashable zip. or somehow one click installer. i imagine if i did, it would only work for this phone, but could be modified for similar devices. i know tcl has a software like that. they plug a phone up and click one button. on their end it's one folder and that program does the rest. that program is what i want to write. reverse engineer this shiz and get a complete understanding of it. i know good and well the folks at tcl aren't sitting on a cmd window using adb to flash dozens of duplicate images time and time again for each device they build. it's screw it together, plug it up, click a button and test. they already have all the files preloaded and they have a preinstaller that pretty much instantly flashes the software. damn, wouldn't it sure be nice to have? but i don't foresee anybody leaking it any time soon. maybe if you have the cheese
Click to expand...
Click to collapse
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me

smuskat said:
Download TWRP for sprout
Download TWRP Open Recovery for sprout
dl.twrp.me
Click to expand...
Click to collapse
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/

R41N MuTT said:
Did you see this? https://www.xda-developers.com/twrp-3-6-0-release-android-11-support/
Click to expand...
Click to collapse
I looked; our REVVL does not seem to be listed in the list of supported devices.
smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
And may I ask for a clarification, please: You wrote above, "the firmware links i sent you- there should be at least 2 different ones, and an OTA... well, if you open the root folder and type 'scatter.txt' in the search bar it will pop up." In your post, I see 2 links to firmware; one is called https://www.mediafire.com/download/sxq4cz8bddmr49l, and one is called https://www.mediafire.com/file/irigs9iviy3sobw/T-Mobile_REVVL_V%2B_5G.zip/file. I downloaded both. I clicked on the downloaded file, and in the search bar, I searched for "scatter.txt", and got no results. What am i doing wrong? Thanks

smuskat said:
I looked; our REVVL does not seem to be listed in the list of supported devices.
Click to expand...
Click to collapse
It needs to be ported still. Unless it's already ported I'm working on it now. Nightmare. I'm trying to follow a guide on here about porting TWRP... Going slow...
OTA
https://r4---sn-npoldn76.gvt1.com/packages/data/ota-api/package/72d80093722599cd459bca02504f22cbf3421dd2.zip?mh=Rs&pl=21&cm2rm=sn-8qj-i5ozd7r,sn-i3bdr7s&req_id=37ad1f0feba7fd94&cmsv=e&ipbypass=yes&rm=sn-8qj-i5olz7l&redirect_counter=3&cms_redirect=yes&mip=117.4.250.39&mm=34&mn=sn-npoldn76&ms=ltu&mt=1672034446&mv=m&mvi=4
Firmware
T-Mobile REVVL V+ 5G
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Here is the link to the scatter.txt for mt6833 (revvl v+).
MT6833_Android_scatter.txt
Shared with Dropbox
www.dropbox.com
Tmobile just recently announced the release of the a13 update. It's supposed to be before the end of february.
Software Updates
Visit T-Mobile Support for help with phones & internet devices, plans & services, billing, and more!
www.t-mobile.com
Message edited at completion of guide. Irrelevant content removed.

After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd appreciate it.

vinnie215215 said:
After installing the modified boot img with fastboot my phone bricked and i cant fix it, it just crashes on boot and loops back whenever i try to normal boot.
If there's any help you can offer I'd
Click to expand...
Click to collapse
Edited: guide complete. Try it now.

R41N MuTT said:
When your phone boots up do you see system font on the screen? It should prompt you to press power to boot normally, otherwise it will continue to reboot. It's because the bootloader is unlocked and you must press power to acknowledge this or else the phone will boot loop. Does this help? If not, get another phone and download magisk and try to patch boot_a again. You can use another device to do all those steps to get the file ready. Pull it, plug in your revvl v+ again and try flashing it. You can also try a different copy of the firmware, I linked 3. You can also flash stock boot_a and boot_b and that should get you going. I'm still figuring this device out. I advise you reach out to somebody who has a lot of experience flashing a/b partition scheme devices, namely mediatek. Project oppo. My only other suggestion is to flash the stock firmware using adb fastboot commands. In the forums you can find a guide to flashing a/b... So, just to be clear, recite to me exactly what you did up to the point it boot loops. And tell me is there system type on the screen when it boots?
Click to expand...
Click to collapse
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\

vinnie215215 said:
So i Followed the guide exactly and everything seemed to work fine until i flashed the img modified by magisk. Fastboot said it moved and wrote successfully.
Then when i rebooted and hit the power button again to bypass the 'orange' warning instead of starting into a factory reset phone, it flashes the backlight and starts booting again.
Im also unable to get into recovery, fastboot mode is all that works now. I've tried to flash the stock boot_a img but not the boot_b, do you think that would help?
I'm gonna make a new img with my s9 and try that as you suggested.
Edit:
Well i might be handicapped.
I had 2 phones here, the V+ and the 6 pro.
Turns out i did youre walkthrough on the revvl 6 pro. It did unlock it, but obviously when i flashed the boot.img for the V+ it bricked. And i cant find the backup anywhere.
In short thanks for your time, I'm afraid all i did was waste it :\
Click to expand...
Click to collapse
Edited to remove irrelevant content. Guide complete. Try it again. If your phone will not hard reboot, try adb reboot bootloader. All activity should cease and your device should promptly enter fastboot.

i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.

contevo said:
i started messing with this phone on my own until ididn't have right stock firm. is alot steps get this phone rooted.
Click to expand...
Click to collapse
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i get this error when loading the scatter file ad i'm using the latest version
v5.1924

R41N MuTT said:
I couldn't agree more. Lol. I'm actively editing the content to condense it. I'm also working on porting TWRP. I've done some other things to save a few steps, like patching boot_a and putting it on Dropbox so all you'll have to do is download it and flash it. When a13 OTA gets captured it'll get better
Click to expand...
Click to collapse
can you help

pickymarker said:
can you help
Click to expand...
Click to collapse
Currently working on it. I've asked a couple ppl for help. Either they'll post here, or I'll update you. Stand by

okay

can it be done today

/

comm-ents said:
I am able to unlock the bootloader, then my phone just hangs at the boot screen, but I can can lock it again Now it just boots with the orange warning and it doesn't matter after that if it is locked or unlocked
The android version is still 11 with a security update from Dec 5, 2022.
I am just curious if there is a way to revert back to a previous version that might just work like the version listed for download. There could also be differences in the boot file that is in the firmware zip file from what is on my phone so patching and installing a different version won't work.
Maybe just waiting until the next version is releases would be the best option?
Click to expand...
Click to collapse
Perhaps that. In fact, that's what I'm waiting on- the a13 update. I intend to capture the OTA and follow the spflash walkthrough. Then I can update this how to where it'll work for everybody. I have 4 people right now with boot issues after root that go beyond WiFi, and they all 4 can't get spflash to work. It's bugging the crap out of me, I haven't been able to figure out what to do to fix it. I'm still waiting on some other folks I've reached out to, if they ever have the time...