Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
C-4Nati said:
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Solved, mod please delete.
C-4Nati said:
Solved, mod please delete.
Click to expand...
Click to collapse
Please post your solution, so others can see it.
C-4Nati said:
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
stevedebi said:
Please post your solution, so others can see it.
Click to expand...
Click to collapse
I went into fastboot usb mode in the bootloader then connected the phone to the computer then dragged the fast boot file inside the sdk rar you download for the One into the command prompt then entered "fastboot erase cache" and hit enter then it let me boot into recovery and I reflashed the rom.
maigre said:
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
Click to expand...
Click to collapse
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
C-4Nati said:
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
Click to expand...
Click to collapse
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
maigre said:
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
Click to expand...
Click to collapse
Yeah I understand. I know I'm going to terminate the insurance I have with T-Mobile soon because I've violated the terms with them. I just have a slight screen lift like many others described on the top and bottom by the speakers and it's not bad at all just noticeable because I inspected it like a mad man when I heard the rumors. I can deal with it easily in it's current state as it's not a problem but if it were to become worse I'm not sure what to do. I know the chances being taken by unlocking as I've always done on every device I've had, I've just fortunately never had a defected device so it wasn't a problem.
4_SUXEN said:
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope that didn't work, I've owned several android devices and did what you just said and it always worked. This is the first time I've owned a non Samsung device in a while (because I used Odin with those) and I couldn't get into recovery at all and factory reset in the bootloader did nothing. Not much experience with fastboot as I've never had to use it but I'm glad I did so I have that in case I need to do it again in the future.
Related
i recently broke my last phone, so i had it replaced and this one is running 2.3.6, i tried using that black white screen (cmd?) with the options ex: 1. unlock root etc.
2. CWM install/root etc etc. x. debugging etc
but no luck ._. is there some guide somewhere?
when i reach the rsd lite portion of the first section, my phone just boots up into the os and rsd lite gets cancelled, any ideas? ( i chose 2.3.4)when i first got it, i could do everything fine, but i couldnt boot after installing 3 different roms.
but when i install clean software it works just as it should
and when i press apply fix for "failure to boot" etc. it unlocks fine, but i cant install roms without it freezing at the dual core screen
Sounds like you got a replacement that motorola locked down the bootloader on. Everything will go as planned but you wont get unlocked. Been happening more and more to people getting replacement phones. Until a different way of unlocking is found (other the sbf flashing or fastboot flashing the unlock files) youre stuck with stock, but you can root. Bad luck.
pre4speed said:
Sounds like you got a replacement that motorola locked down the bootloader on. Everything will go as planned but you wont get unlocked. Been happening more and more to people getting replacement phones. Until a different way of unlocking is found (other the sbf flashing or fastboot flashing the unlock files) youre stuck with stock, but you can root. Bad luck.
Click to expand...
Click to collapse
how do i fastboot flash the unlock files? and since this phone is older, would anyone even try unlocking the newer models?
and im VERY disapointed in these new models, mabye its just mine, but on mine, the screen is litterally popping out, and theres a faint white square that borders the actual lcd, and the on/off/fingerprint scanner barely has any click so its hard sometime to know if u pressed it or not .... damn you moto, im not buying another one of your phones after this one, HELLO GS3 :d
wasssabi5 said:
how do i fastboot flash the unlock files? and since this phone is older, would anyone even try unlocking the newer models?
and im VERY disapointed in these new models, mabye its just mine, but on mine, the screen is litterally popping out, and theres a faint white square that borders the actual lcd, and the on/off/fingerprint scanner barely has any click so its hard sometime to know if u pressed it or not .... damn you moto, im not buying another one of your phones after this one, HELLO GS3 :d
Click to expand...
Click to collapse
If youre already seeing those type problems, you might want to notify warranty department again. Sounds like a dud replacement. As for the fastboot thing, check out the stockier noob guide first then search for those files. I dont have them anymore or I'd pass em to you.
Sticky, not stockier
I can help you using the same process I went through with my phone, but I have to warn you I won't be responsible for anything that happens to your phone. If interested PM me
sent u a pm but u didnt answer
when i open into recovery and go into twmp and i go to reboot>recovery it says no os installed. my recovery is completely gone. what do?
Ok so I was searching, a lot, and found that I can turn the phone back to OEM. unfortunately every guide I have read says it needs to be s-off using firewater. When i do the "adb reboot" function it gets stuck at the htc boot screen and I cannot perform the second step in making the phone s-off. what do I do? Is my phone legitimately bricked? Like hard bricked forever?
I also ran the RUU. It goes through and when it gets to step 1 of 7 it stops and says "unknown error occurred" I go through the error recovery steps and it still does not work. Just trying to keep all the info here so you understand the situation I'm in. It also boots into recovery mode, obviously, with the power button and volume down button.
got it. could go ahead and delete post.
Don't have the thread deleted, but instead explain how you finally solved the problem so others may learn from your experiences...
-Sent from a payphone...
tttomdemaria said:
Ok so I was searching, a lot, and found that I can turn the phone back to OEM. unfortunately every guide I have read says it needs to be s-off using firewater. When i do the "adb reboot" function it gets stuck at the htc boot screen and I cannot perform the second step in making the phone s-off. what do I do? Is my phone legitimately bricked? Like hard bricked forever?
Click to expand...
Click to collapse
I know you've already sorted it out. But first, this phone is not bricked if the screen comes on. Recovering is usually not hard at all, just a matter of knowing how to do it.
Second, were you referring to a warranty claim for a phone being not bootable due to mods that you did? That isn't covered under warranty, and is immoral. Take responsibility for your actions; and don't jump the gun and think you have to get a new phone after just a couple hours of unsuccessful attempts to get the phone running. If you want to root and mod these devices, you are going to have to learn to be patient and work through little quirks like this.
Lastly, the phone needs to be bootable to perform firewater s-off.
Thanks. yea my only two friends that do this kind of **** are like seriously the most pessimistic, negative assholes I have seriously ever met in my life. They kinda just scared me into thinking it was easy to brick a phone and totally mess it up. After some research i just found all I had to do was run an RUU and make sure the phone was relocked.
seriously. they are real negative nancies.
Ok for those of you who may ever be in the situation I was in I will write up how i fixed it. very simple and took probably about 20 minutes start of download of tools to finish. This was done on windows 7 but i'm sure it is pretty similar on windows 8 as well.
In order to do this you will need to know that holding the power button AND the volume up button simultaneously emulate a battery pull and that holding the power button AND the volume down button enter recovery mode. If you are stuck in a boot screen or splash screen like I was you will need to emulate a battery pull and them immediately switch to enter recovery without actually removing your finger from the power button.
Then you need to make sure you have the right tools. you can find them at these locations.
RUU- http://forum.xda-developers.com/showthread.php?t=2757462
ADB- http://www.mediafire.com/download/5s2nfws9wkj9gyq/adb-fastboot.zip
Now you need to make sure your phone is either "***LOCKED*** or ***RELOCKED*** when you enter the recovery mode.
You can do this very easily. Plug your phone into your computer and enter recovery mode. Make sure the phone is in Fastboot USB mode and not Hboot. Open the folder titled "Android" in the adb kit you downloaded from the link above. Shift + right click anywhere on that folder(not on a file) and choose "Open command window here" type in the command window "fastboot oem lock". It will show as "relocked" after you do this and it reboots. This will allow you to run the RUU without any issues. Always make sure the phone is in "Fastboot USB" mode.
Now run the RUU executable and it will automatically pick up your phone assuming all of your drivers are in order. Just hit yes to everything and it will run through what it needs to. If you do not have a progress bar on your phone's screen as well as your computer then you messed up somewhere. start over.
If you try to do this on the At&T htc one (m8) without actually relocking it first the RUU will fail at step 1 of 7.
Good luck.
tttomdemaria said:
Thanks. yea my only two friends that do this kind of **** are like seriously the most pessimistic, negative assholes I have seriously ever met in my life. They kinda just scared me into thinking it was easy to brick a phone and totally mess it up. After some research i just found all I had to do was run an RUU and make sure the phone was relocked.
seriously. they are real negative nancies.
Click to expand...
Click to collapse
Then stay away from those guys! Sounds like they don't really know that much, wrong attitude, and you are probably already on your way to knowing what they know, if not more.
This phone is pretty hard to brick. As long as you aren't flashing hboot or radio, and don't flash anything intended for another device, its pretty difficult to brick this phone by modding it. The condition you were in was not a brick, and not even close. Some call this a "soft brick" but in my opinion, there is no such thing, its either bricked (requires opening the phone to recovery, such as JTAG or replacing motherboard) or its not. What I call it is "something is wrong with the phone and you just need to do the right steps to get running again".
---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------
tttomdemaria said:
Ok for those of you who may ever be in the situation I was in I will write up how i fixed it. very simple and took probably about 20 minutes start of download of tools to finish.
Click to expand...
Click to collapse
Glad you sorted it out, so nice job.
Although RUU was probably a little overkill. RUU is a useful recovery tool, although a bit of a nuclear option. But good last resort. Since you RUU'ed, you will need to unlock the bootloader again, and flash custom recovery to get back to where you were originally (phone setup for mods) if that is the intention. If the intent was to go back to stock and stay there, RUU is a great way to do that.
You probably could have just gotten back up and running by using adb to wipe cache, re-install custom recovery and flash a ROM.
Information available:
Boost site: https://www.boostmobile.com/phones/coolpad-legacy.html
Manufacturer details: https://coolpad.us/legacy-boost/
Youtube video I made: https://www.youtube.com/watch?v=wylMivqymUM
This phone was purchased from Walmart and obviously they are no help. Went to a Boost Mobile and a Verizon store and neither one could do anything either (BTW huge props to Verizon on their customer service). I need to know how to clear this phone of all prior information (which is seems that a factory reset from within the OS does not do) and also how to get into the bootloader. Normal physical button methods like power+volume down or up or all 3 just make it say "official" on the screen and then it boots anyway. How do I hack this thing? I've gotten into literally hundreds of Android phones that were bricked and this is the first time I have had this new problem and I don't know where the blame lies. Even if there is a halfway legit custom ROM I could put on the thing, I don't know, I've tried everything I can think of. Can anyone help?
Thank you in advance!
adrenatek said:
Information available:
Boost site: https://www.boostmobile.com/phones/coolpad-legacy.html
Manufacturer details: https://coolpad.us/legacy-boost/
Youtube video I made: https://www.youtube.com/watch?v=wylMivqymUM
This phone was purchased from Walmart and obviously they are no help. Went to a Boost Mobile and a Verizon store and neither one could do anything either (BTW huge props to Verizon on their customer service). I need to know how to clear this phone of all prior information (which is seems that a factory reset from within the OS does not do) and also how to get into the bootloader. Normal physical button methods like power+volume down or up or all 3 just make it say "official" on the screen and then it boots anyway. How do I hack this thing? I've gotten into literally hundreds of Android phones that were bricked and this is the first time I have had this new problem and I don't know where the blame lies. Even if there is a halfway legit custom ROM I could put on the thing, I don't know, I've tried everything I can think of. Can anyone help?
Thank you in advance!
Click to expand...
Click to collapse
You can get to fastboot via adb. I can't get the bootloader to unlock tho.
@adrenatek, I know this is a belated reply, but I just got one of these devices myself and wanted to chime in. Let me see if I understand correctly: are you stating that, after performing a factory data reset, your userdata remains intact on your device? Or, did you get it figured out by now? Also, as to fastboot mode, adb reboot bootloader will get you there, but this device is not supported for OEM unlocking.
can anyone tell me if i can unlock the BL of C3505L..
I was playing with it, wanted to root it and boot into twpr, but before i could do any of that, i was stuck in recovery mode! First time i restarted it into recovery to figure out how to get into twpr, i got to this screen, entered my pin 3362 and proceded to next menues, didnt find what i wanted so i selected enter to recovery again, phone restarted got to this screen again, but now my touch screen isn't working! I cant type anything! And i cant get past it! I can sthut it down, restart it, go to fast boot mode, but everything leads me to this recovery screen again where my touchscreen isnt working and i cant type my pin or anything!
DAMN THESE CHINESE SOFTWARE ENGINEERS.... i will give my phone back using warranty claim, hopefuly those morons wont fix it and ill just get a new one.... but maybe they will just give me big .I. because i live in corrupt country where law means nothing, so i wanna try my luck here.... anyone have any idea how to fix this?
I'm a newby in this things, once i menaged to unbrick my old chinese phone elephone P something, it took days of googleing trials and errors, but i menaged to install new android version which wasnt supported by my elephone.... but microphone didnt work tho xD So yall need to explain things to me in details coz im pretty noobish, but i can menage....
Man... this sucks so much..... how bad could these engineers be, i cant be first person this happened to, and this is surely a bug that isnt fixed, and i kept my phone up to date.
Happens to me as well. You can still use the volume keys to navigate around; however, you may not be able to go back once you select something. Unfortunately the only way I got around it was by installing a diff recovery, either twrp or the pixel experience recovery kronflux uses.
Don't use twrp on this phone.
Seriously. Do not.
Also, that's not recovery. That's your bootloader menu and only works through using your volume keys and the power button.
(Side note, warranty won't cover a modified device and attempting to turn in a device that's been altered can hurt later attempts at using your warranty for legit concerns.)
ninjasinabag said:
Don't use twrp on this phone.
Seriously. Do not.
Also, that's not recovery. That's your bootloader menu and only works through using your volume keys and the power button.
(Side note, warranty won't cover a modified device and attempting to turn in a device that's been altered can hurt later attempts at using your warranty for legit concerns.)
Click to expand...
Click to collapse
There are 2 pictures, second one is bootloader, yes i navigate using volume buttons, first one is recovery that asks me for password, which i can't type, because ''screen'' stopped working, and i cant get pass these screens. Did you even read my post or just saw it with left eye and decided to type a comment so i have to repeat what i allready said?
Anyways, i returned phone under warranty, and i didnt get to root it with twpr even tho that was what i was trying to do, but phone bugged out on me beforehand. Hopefully they wont give me any problems because i did ''install'' twpr in os, but that probably means nothing as it doesnt really do anything at that point.
I was following tutorials i found for this specific phone, probably bullcrap generic articles, i wont try to root it again because it seems like a problem, **** oneplus....
But, if they dispute my claim and ask for money, they wont get any, i will ask them to return the phone to me and i will manually flash it completely or whatever, and get it working. I was refraining from doing so because its under warranty and i didn't want to **** it up.
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
OnePlus will not do anything due to the warranty being void...
DM me. I can work this out with you. I ran into a similar problem.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
Tried sending it for repair but had the op guy look up my imei and ITS A DAMN DEMO PHONE I GUESS!? Cant return it, bought off amazon refurbrished and due to my anger problems i shattered the screen but other than that i shouldnt of been sold a damn demo phone from the start.
T3CHN0T33N said:
OnePlus will not do anything due to the warranty being void...
Click to expand...
Click to collapse
they would repair it, they even repair tmobiles version and metro and all but it really ticked me that amazon refurbrished sold me a demo phone or the phone is now thinking its a demo phone somehow..
Springles2 said:
DM me. I can work this out with you. I ran into a similar problem.
Click to expand...
Click to collapse
Never discuss in DMs! This person has illegitimate intentions.
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
it's not against the rules it's just not a good idea to do
T3CHN0T33N said:
it's not against the rules it's just not a good idea to do
Click to expand...
Click to collapse
Thank you for the advice! Just wanted to see if I could legitimately help!
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
illegitimate intentions, lol what are you trying to say? didnt know my intentions had any type of rules to be followed.
if oneplus sends people on the daily unlock codes in order to unlock their bootloaders on their phones, shouldnt people be able to explore some other OS's and things of that sort? My intentions were to TEST out GSI's that developers worked hard on to work with certain devices and provide some feedback and hopefully come along one that i can use on the device as a daily.
This is Forums, know your place. I think we are all a lil illegitimately intentional at times dont ya think?
no offense.
Springles2 said:
Thank you for the advice! Just wanted to see if I could legitimately help!
Click to expand...
Click to collapse
Thanks for your gratitude.
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
jerryhou85 said:
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
Click to expand...
Click to collapse
Thank you for explaining it to others who might need it
Also, will never ask for anyone’s personal info or financial info or anything to do with their identity. That is their information and have no interest in knowing more than their username on here
Maatt_OG said:
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
Click to expand...
Click to collapse
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Maatt_OG said:
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Click to expand...
Click to collapse
Please write something up on how you did it! It could save someone!
Springles2 said:
Please write something up on how you did it! It could save someone!
Click to expand...
Click to collapse
Well at times it would just bootloop nonstop after using the msmtool, but then tried entering safe mode and that was a success but remembered each time it went to turn on the wifi to set up the phone it would freeze and bootloop no matter what,
So from emergency call find your way into permission manager , from there you can open settings app, disable location and anything that would trigger wifi to turn on , airplane mode is on remember this, you need to turn it off withput having the wifi kick on. Disabling some modem/network apps or that has anything to do with wifi, location, carrier, modem that you can disable, do it. Once you're able to turn airplane mode off successfully you can get passed the wifi part of the phone setup and use your mobile data instead, or what I did is use gnirehtet , you can find it on GitHub. Install on PC, make sure you enable USB debugging and have the default USB config set to USB tether, not hotspot .extract zip to platform tools, Move the apk file from gnirehtet zip to your phone, run the provided command from the zip and you'll get a request to allow debugging on your phone from PC, once you do that. You'll finally be able to update your n200 T-Mobile phone to Android 12 which is the only way I found to do this. Make sure you update to Android 12 and not another android 11 before turning wifi on or anything else or you will have to start ALL OVER. Done it twice it's a pain in the arse
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
I was going to say keep discussion in the open in case any future people come across the same issue. If there's one thing I hate is coming across the same issue as my issue on stack overflow or elsewhere and OP from 7 years ago saying, "Never mind, I figured it out."