I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Zehmistah said:
I've got the Canadian Virgin Mobile Moto G, and I recently unlocked the carrier. I am going to unlock to bootloader to flash a rom with more languages, specifically Portuguese.. What rom should I use, I'm looking for the original Moto G software.
Click to expand...
Click to collapse
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Z-WolF said:
I'm running CM11 and a quick look the phone tells me that it have Portuguese for brazil and portugal, alternatively try any latin american stock rom: http://sbf.droid-developers.org/phone.php?device=14
Click to expand...
Click to collapse
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Zehmistah said:
Oh man, thank you for the link, I just might use that. Just a refresher, to flash It I would first unlock the bootloader, flash a new recovery, wipe, and then flash the new rom?
Click to expand...
Click to collapse
yep, but you don't need to flash a custom recovery for a Stock ROM.
Z-WolF said:
yep, but you don't need to flash a custom recovery for a Stock ROM.
Click to expand...
Click to collapse
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Zehmistah said:
Thank you!!! and one more question, the new rom should still be capable of getting OTA updates from whatever carrier's rom I flashed, correct?
Click to expand...
Click to collapse
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Zehmistah said:
****. I think I ****ed up. http://forum.xda-developers.com/showthread.php?t=2727965
Click to expand...
Click to collapse
Zehmistah said:
Okay so I unlocked my bootloader for my Moto G, and when It rebooted it said android was updating apps and then all the processes stopped working. It booted into the android startup but I couldn't get any processes running so it wouldnt work. I tried to reboot and now android doesn't even boot up. Should I flash a custom recovery right now and then wipe??? I haven't done anything to the phone other than carrier unlock and bootloader unlock. please help
Should I try this? http://forum.xda-developers.com/showthread.php?t=2542219 , or is it too risky right now? I'm planning to restore it to another stock firmware anyways.
Click to expand...
Click to collapse
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
They all want money.
Sent from my GT-N7105 using xda app-developers app
Perry2547 said:
They all want money.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate?
You can add more languages without a custom ROM using MoreLocale 2.
Z-WolF said:
First, don't panic.
Second, explain how do you unlock the bootloader, did you use this?
Third, what does the bootloader screen (Power+VolDown) says in the second to last line before the first break (LOCKED/UNLOCKED).
Fourth, if it says UNLOCKED, try to flash the ROM using this, otherwise try to unlock the bootloader again with the link i posted in the second point.
And don't worry as long as you can enter fastboot mode (bootloader) you can fix everything, and nothing of the things you are doing affects fastboot mode.
Click to expand...
Click to collapse
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Zehmistah said:
I used that webstie to unlock the bootloader, and when I went to fastboot it did say UNLOCKED status code: 3.
I left it plugged into my PC last night because It wouldn't turn off, and I think it wasn't charging because now it's off and won't turn on. I'm going to plug it into a wall charger and wait a few to check if it's on.
After that, I'll try the method you said.
EDIT: Seems like charging doesn't work either, weird... because it said it was connecting to my PC last night in Fastboot
Click to expand...
Click to collapse
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Z-WolF said:
That's weird, doing the steps in that page don't make changes big enough in the phone to make something like that happen.
What does it says in the line below UNLOCKED, USB CONNECTED or CONNECT USB DATA CABLE while you had it connected to your pc/wall?
Why don't you try to use another cable?
Click to expand...
Click to collapse
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Zehmistah said:
I don't remember what it said.
I've tried a few different wall chargers and cables. They seem to charge my other phones but not this one. I'm going to wait an hour and then maybe put it in the freezer for a few minutes
Click to expand...
Click to collapse
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Z-WolF said:
That's a... unorthodox approach, but reading around it just might work.
I can only recommend you to put it in a sealed container and having a rice bag at hand afterwards, just in case.
Now if you can get it to fastboot mode, try to restore a backup (if you did one) or flash a ROM, im assuming that if you can connect a cable and send commands to fastboot it is charging the phone. BTW at this point if you can send commands and are tired trying to fix it, you can execute
Code:
fastboot oem lock
and you can claim the warranty, that behaviour is not normal, maybe something in the hardware side broke but until we test it more we can't be sure.
Now while we wait in for the phone to become a popsicle, can you detail how you unlocked it?
Click to expand...
Click to collapse
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Zehmistah said:
Ok, so I bought the phone and got it carrier unlocked, then yesterday I decided to flash a new rom to get the languages so I went to https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth. Unlocked the bootloader and when the phone was about to restart from cmd it said "FAILED" but rebooted anyways. It went into fastboot again and ti said it was Unlocked, when I selected Normal Reboot, it started up with the bootloader logo and continued on normally. It was then that it displayed the android startup page (Where you select language, sign into google, connect to wifi etc.) like I haven't used the phone before. Shortly after a popup came and said " Android is updating # of apps out of 137", once that was over every single process on the phone crashed.
Now I'm where I am now.
One more thing, I booted it into recovery before I unlocked the bootloader, accidently. Do you think it maybe could've wiped the original OS on the device?
Click to expand...
Click to collapse
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Z-WolF said:
As far as i know, you can't wipe the system with a stock recovery and with a "blank" OS your phone still connects to PC.
i forgotted this existed, at this point you can't lose anything in trying it. i dont recomend the bootloader bricker part for your case.
Click to expand...
Click to collapse
The phone isnt't being detected when I plug it in.
I've read that leaving the phone 24 hours untouched could also help the battery. I'm going to try that\
EDIT: GOT IT TO TURN ON!!!
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Zehmistah said:
Ok, so I got it working. The thread you told me first helped!! It works fine now with the Brazilian software. Thank you very much, you're a life saver.
Now... I've got another moto G to do the same to
Click to expand...
Click to collapse
You had me worried there, i though it was a goner. in the end everything turned out okay.
Happy to be of service.
Related
I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.
pintyguy said:
I have the Razr HD running stock 4.1.2, rooted, today i started getting the OTA update install requests, well i accidentally hit install, so now my phone will boot up just fine for a minute, i can even unlock it an navigate for about 20 seconds, then it automatically powers back off, an boots up into
AP Fastboot Flash Mode
device is locked, Status Code: 0
Battery OK
Connect USB data cable
failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Tried to boot it back up in recovery through fastboot, an get the same message. I'm not sure where to go from here, any help would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Because you installed it over a rooted phone (which is strange, as it shouldn't work) you're best bet is to flash it back to stock KK, especially if it already applied the trusted zone updates.
Of course, updating to KK 4.4.2 will then allow you to unlock your bootloader.
So, the first step is to flash to KK 4.4.2. Go here and follow the steps (it should keep your data so you won't lose what is on your internal SD card but you WILL lose all other app settings) -> http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
Once you have followed all the directions (read, read and read again BEFORE you attempt to do anything), then go here to root and unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-info-status-of-root-for-kitkat-build-182183/
Hopefully, you didn't get the latest OTA, If so, you might be hosed as far as getting your bootloader unlocked, but I don't think they've pushed out the latest patch to KK for the XT926.
That should get you back up and running. Again, you will lose your app data (that is not stored on the internal SD card), but your internal and external SD cards will be left alone and intact.
I'm going to try, only problem i foresee is that i need to boot into AP Fastboot to be able to flash, but everytime I try it brings me back to the same error screen. Since that screen is technically AP Fastboot Flash Mode, Im going to try an flash it from there, but Im not sure. Will let you know what happens.
update
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.
pintyguy said:
So I flashed the new KK as suggested, which was a process in itself, but I got it working anyways. Now I cannot get connected to the mobile network though. It shows my phone number and everything, it just says mobile network disconnected, so I can't make calls or text at all. I'm attempting to connect to T-Mobile BTW, if it makes any difference. Any ideas? Does it have anything to do with the fact that I haven't unlocked the bootloader yet? Not sure why it would, just curious.
Click to expand...
Click to collapse
do you have xt926 or xt925
Sorry, but what's the difference?
1 :angel:
pintyguy said:
Sorry, but what's the difference?
Click to expand...
Click to collapse
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?
Yes it does
pintyguy said:
Yes it does
Click to expand...
Click to collapse
then you must have previously done the modem unlock you will need to redo it that is all
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
pintyguy said:
Yes it does
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2389740
that should be the thread for how to do it tell us how it goes, i have no experience with this i am still on Verizon but others say after writing to the phone wait 5 minutes not seconds sorry i rembered wrong before rebooting other wise the settings will not stay
Awesome I was just about to ask for a link, thank you. And I actually got this phone pre-rooted and everything, so the guy before me must have flashed the modem. When I got it I just dropped T-Mobile sim in and it worked just fine. Luckily I'm not new to any of this, I just had a Galaxy s3 running CM11 I believe, but got rid of it and got this. Again, appreciate all the help. Gonna give it a go now and I'll report back soon.
billycar11 said:
one is a Verizon phone the other is for other carriers
does your phone have Verizon branding on it?
Click to expand...
Click to collapse
Well I'm about at my wits end on this one. I couldn't get the Moto Diag driver to correctly install to port, so I went with the RadioComm method instead. I followed a tutorial off this site, which I can't link to just yet asbi do not have enough posts. But followed it to a tee, and it seemingly was successful. But after reboot I only showed bars for about a minute, then right back to no service, T-Mobile could not be registered at this time. Nowhere in the comments or in the guide did they mention to wait the 5 minutes after writing with this method, could that possibly be why? I'm really starting to get frustrated at this point...
Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.
pintyguy said:
Alright, so after 3 days of tirelessly pouring over the forums and two different laptops, I'm finally back up and running. I couldn't get the Moto Diag drivers to correctly install to the port, on either computer, (one was running Windows XP SP3, the other Windows 7x64)so using CDMA WS was out of the question all together. I ended up following the tutorial on using RadioComm to flash the modem instead. First attempt was successful, but I immediately rebooted when it was finished writing, and apparently it didn't stick. So I went back, checked first, and it had reverted back from "00" back to "01",meaning it was locked again. So I rewrote it, and this time left it plugged in after if finished for about 10 minutes, then rebooted, and voila, back up and running, no problems since. I repeat, if you are flashing the modem, whether it be with CDMA WS, or RadioComm, YOU MUST WAIT AT LEAST 5 MINUTES AFTER FLASHING BEFORE REBOOT, otherwise it will not stick and your wasting your time. Thank you for all the help, it is very much appreciated.
Link for the RadioComm tutorial I ended up using:
http://forum.xda-developers.com/showthread.php?t=2166542
On a side note, is it really worth unlocking my bootloader? I realize I'm right at the list version where is possible, and all over the forums it's threatened "UNLOCK NOW OR STAY LOCKED FOREVER!", just curious if it's really worth the time and effort. But again, thanks to everyone who helped, and if I may assist anyone else in a similar situation feel free to ask.
Click to expand...
Click to collapse
it is worth it also i told you about the 5 minute thing
billycar11 said:
it is worth it
Click to expand...
Click to collapse
I thought I was going to lose my data, didn't realize motopoc would do it without losing everything, so I figured might as well.
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Colday96 said:
Hi guys
As you probably know by reading the title, i completely messed up. I was on the stock google factory image and decided to flash a custom kernel. I enabled usb debuging and oem unlock. after having unlocked the bootloader, I installed the twrp boot img and then flashed the kernel. All was well when i stupidly decided to lock my bootloader. Things crashed and now when i try to boot into my phone, the google logo appears and 1 seconds later crashes keeps doing it until i turn my phone off. My bootloader is locked and i think usb debuging and oem unlock are also disabled.
The same thing happens when i try to go to the recovery, it just crashes.
Any help would be greatly appreciated guys. thank you !!
Click to expand...
Click to collapse
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
phaino00 said:
I feel bad for you. However, you bricked your Pixel.
As I mentioned yesterday, contact Google for an RMA replacement.
Click to expand...
Click to collapse
I bought the phone on ebay. Could i still get a RMA replacement ?
Colday96 said:
I bought the phone on ebay. Could i still get a RMA replacement ?
Click to expand...
Click to collapse
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
If you bl locked the phone w modified software ur boned. I believe that RMA availability is transferrable from owner to owner, however, I also believe that they will refuse to RMA a phone which technically broke because AVB is doing its job properly. You can try but I'd say your chances are slim. Sorry mate. Also future reference: if you don't have any reason in particular to relock your phone, just don't. You'll save yourself the hassle of having to do it again and it wiping the phone everytime any software thing goes wrong or anytime u want to upgrade custom ROM or kernel or anything of the sort. This goes for any phone not just those with android verified boot.
phaino00 said:
I don't believe so since you're not the original owner. However, it doesn't hurt to try.
Click to expand...
Click to collapse
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Assume they will.
Colday96 said:
My seller is about to contact google to get a replacement. do you think google will know if i did something with it i shouldn't have ? Since i can't boot in the recovery, won't they be able to do it either ?
Click to expand...
Click to collapse
Yes they will know but they have proprietary software to forcefully unlock/reformat the phone properly if they so choose to actually accept the phone
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400 ?
Click to expand...
Click to collapse
You can still sell it for around 150 for parts on ebay
Nandolkz said:
This just happened to me today, i was trying to reset it because I'm selling this phone and boom.. Brick... Just lost $400
Click to expand...
Click to collapse
Can't you restore using the stock zips from google?
Poebat said:
Can't you restore using the stock zips from google?
Click to expand...
Click to collapse
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Nandolkz said:
I already tried, using both 8.1 and the first Nougat... It says oem can't unlock. I even download the skipsoft app to tryout but fail
Click to expand...
Click to collapse
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Poebat said:
If you are flashing the latest version of Oreo you don't need to oem unlock. What version of Android were you running before you bricked it?
Click to expand...
Click to collapse
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Nandolkz said:
8.0, well I already tried the dic 8.1 and it didn't work... Let me try the nov build.. or im going to try both let me see what happen.. I'll share the cmd log...
Click to expand...
Click to collapse
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Poebat said:
Okay. If that doesn't work try the 7.1.2 build with the flash-all.bat
Click to expand...
Click to collapse
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Colday96 said:
It won't work because his bootloader is locked. I also tried the OTA file and that didn't work either. Do to have usb debugging on ?
Click to expand...
Click to collapse
He doesn't have a working OS so I doubt it
Here is what is happening to me... Any ideason how to fix it? ?
Nandolkz said:
Here is what is happening to me... Any ideason how to fix it? ?
Click to expand...
Click to collapse
Try flashing the stock rom with fastboot
Poebat said:
Try flashing the stock rom with fastboot
Click to expand...
Click to collapse
Here
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Passportpowell said:
I haven't turned this phone on in years.
I unlocked the bootloader and flashed roms years ago and i remember trying to get it back to stock and trying to relock it but i couldn't fully do it.
I tried to install TWRP and put a rom on it but it wont work so i thought trying to get it back to stock as much as i can might help. then i can start again
1. the phone doesn't work by USB if plugged in while it's on. I have to leave it plugged in and then restart it for it to work
2. ADB works while phone is on (doing 1)
3. Fastboot does not and i have no idea why. I can't install TWRP
Click to expand...
Click to collapse
do you have usb debugging enabled, are your sdk tools up to date?
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Passportpowell said:
Yes to both.
When doing the adb fastboot part it restarts into one of the screen I attached to my post.
My computer makes a noise like a USB had been connected but nothing comes up.
fastboot devices command shows nothing and when I check device manager it just says android with a yellow! If that helps.
Click to expand...
Click to collapse
then you need to update your htc drivers.
here you go.
Aldo101t said:
do you have usb debugging enabled, are your sdk tools up to date?
Click to expand...
Click to collapse
Aldo101t said:
here you go.
Click to expand...
Click to collapse
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
I've done a format data on twrp and it won't ask for a password anymore but I still can't sideload anything. Going to try to copy the rom to the storage and see what happens there
I've only could see a twrp folder on my phone when I connect it to my pc while still in twrp so I copied a rom there and went into install zip, data, media, twrp. My file was there.
Installing rom now I'll update if it worked.
Passportpowell said:
Super star
I now have another issue though. I can't sideload and it's asking for a password for twrp to mount decrypt data. If you don't mind trying to help me here too
View attachment 5087597
View attachment 5087599
Click to expand...
Click to collapse
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
here is magisk
if you are on pie that viper rom is based on oreo. just so you know.
Aldo101t said:
you may have to format data, then flash magisk after then reboot, why are you trying to side load the rom just put it on your ex-sdcard, and flash it in twrp. twrp won't decrypt your data, what version of twrp you using, the latest is 3.4.0-0
try hitting cancel when it asks for a password, then see if it works.
Click to expand...
Click to collapse
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Aldo101t said:
if you are on pie that viper rom is based on oreo. just so you know.
Click to expand...
Click to collapse
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Passportpowell said:
Yeah i sorted that bit. it confused me because there were no files and didn't know how to get to anything i copied over but that's how i got the rom on
Yeah i realised after you said it. I believe i was on pie because i was on build no. 3.34.401.1 and now i'm on 2.33.401.19 after installing the rom. I shouldn't be trying to do this at almost 12:30 at night haha.
Is that bad that its gone through and, so far, worked? What would you recommend I do/ what would you do if you were in my position currently?
I was originally going to to try to get back to stock but im not even sure what RUU to use as i think the one that i had used a few years ago might not have been the original.
you've been an amazing help so far so thank you
Click to expand...
Click to collapse
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Aldo101t said:
well, see how it goes, if you start to have issues go back to stock, if you made a backup of stock just restore it.
use the ruu for 401 make sure it's 3.34.401.x
that software number doesn't mean you are on 2.33 firmware you'll still be on pie firmware, 3.34
Click to expand...
Click to collapse
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Passportpowell said:
I can't seem to find a RUU for 401 3.34.401.x that isn't dual sim version. Could you point me in the right direction please in case I do ever want to attempt stock again?
Edit: I've found it. Also why this one instead of 3.37.617.1?
Edit: im guessing because 3.37.617.1 is for NA and the one you mentioned is for EU which is where i am
Also I think im getting an idea about why it won't charge or connect until I restart.
I've installed lineage room 17.1 and it's constricted showing as "charging connected device via usb" even when it's nothing is plugged in. I'm guessing it's a hardware issue?
Click to expand...
Click to collapse
3.37.617.1 is for the us-unlocked
Hello to everyone...I just got from my older brother his HTC U11 4gb 64gb phone. And it has locked bootloader and does not have root. So please what should I have to do so I can install custom rom. Stock rom is old full of bloatrware. There is so many information that I am confused.
Thx so much !
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into fastboot mode.
All the usual processes have been eliminated...enabled Developer options, enabled OEM Unlock for Bootloader, enabled Usb debugging, etc...all ready, set, don't go.
I powered off the phone, restarted while holding the power+vol dwn, pwr+vol up, pwr+vol up and down, pwr+assistant key, pwr+vol up+assistant key and every combo thereof including every combon with the battery removed and USB connected while keys pressed. I gotta get to this fastboot or I'll go nuts...PLEASE!! Somebody help!!
Check whether Fastboot is supported or not via ADB
Code:
adb devices
adb reboot fastboot
fastboot devices
If a connection with bootloader got successfully established don't forget to end it
Code:
fastboot reboot
TCL is never known to have offered BL unlock for any of its device. On top of that, US carriers tend to enforce non-unlockable BL, Straight Talk / Tracfone (implied by the DL suffix) the worst among them.
jwoegerbauer said:
Check whether Fastboot is supported or not via ADB
Code:
adb devices
adb reboot fastboot
fastboot devices
If a connection with bootloader got successfully established don't forget to end it
Code:
fastboot reboot
Click to expand...
Click to collapse
Hi I have tried all of the above commands and about a dozen more. I'm tempted to believe what
I was recently told, that US Phone maker enforce the no Unlock bootloader policy. There would still need to be some window or method available for flashing in the event of a software failure, right? In the Developers menu it says the bootloader is already unlocked and the toggle is grayed out. When I reboot from ADB using adb reboot fastboot my phone reboots back to startup with no fastboot connection??
I also happened on one of these TCL A3's (A509DL), and I confirm that there is no fastboot mode, and only 3 options in recovery, no adb or sdcard or log access, strictly factory wipe and cache wipe.
Hopefully mtkclient will crack this baby open a little bit, I left my laptop in a friend's truck, but when I get it back here in a few days ill hack the crap out of it!
NashvilleKarl said:
I also happened on one of these TCL A3's (A509DL), and I confirm that there is no fastboot mode, and only 3 options in recovery, no adb or sdcard or log access, strictly factory wipe and cache wipe.
Hopefully mtkclient will crack this baby open a little bit, I left my laptop in a friend's truck, but when I get it back here in a few days ill hack the crap out of it!
Click to expand...
Click to collapse
Hey bro. Thanks for responding. Let me know how it goes. I can't even find Stock Firmware for this little pain. Mine is branded TCL A509DL a friend has the exact device thru Cricket branded Alcatel with a different model number but same deal zero fastboot or bootloader for fastboot. Now I HAVE to crack this pain.
Try with python mtkclient , not responsible, you got to know what you're doing, very easy to brick
JansenLove said:
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into fastboot mode.
All the usual processes have been eliminated...enabled Developer options, enabled OEM Unlock for Bootloader, enabled Usb debugging, etc...all ready, set, don't go.
I powered off the phone, restarted while holding the power+vol dwn, pwr+vol up, pwr+vol up and down, pwr+assistant key, pwr+vol up+assistant key and every combo thereof including every combon with the battery removed and USB connected while keys pressed. I gotta get to this fastboot or I'll go nuts...PLEASE!! Somebody help!!
Click to expand...
Click to collapse
Hey just tried and succeeded, using python Git and mtkclient from https://forum.xda-developers.com/t/blu-b130dl-unlock-recovery-root-release.4350825/ basic same principle just swap around a few files and it worked, a509dl tcl a3 is rooted, not responsible for any damage to device, I hope y'all know what your doing
bbcdt22 said:
Hey just tried and succeeded, using python Git and mtkclient from https://forum.xda-developers.com/t/blu-b130dl-unlock-recovery-root-release.4350825/ basic same principle just swap around a few files and it worked, a509dl tcl a3 is rooted, not responsible for any damage to device, I hope y'all know what your doing
Click to expand...
Click to collapse
I just got a tcl a3 (a509dl), dumping the firmware right now with mtkclient. I had driver problems with Windows (ghostspectre 11).. used the 're_livedvdv3' bootable iso. So far so good
Woo thank you for the info ! Unlocked and magisk rooted. Do we have twrp for this device on xda?
JansenLove said:
Hey bro. Thanks for responding. Let me know how it goes. I can't even find Stock Firmware for this little pain. Mine is branded TCL A509DL a friend has the exact device thru Cricket branded Alcatel with a different model number but same deal zero fastboot or bootloader for fastboot. Now I HAVE to crack this pain.
Click to expand...
Click to collapse
I lost my dumps, long story.. I need the stock firmware for this phone also, I bricked mine messing around lol even just The boot.img and vbmeta might be all I need can anyone with this phone grab them w mtkclient and upload ??
iamx51 said:
I lost my dumps, long story.. I need the stock firmware for this phone also, I bricked mine messing around lol even just The boot.img and vbmeta might be all I need can anyone with this phone grab them w mtkclient and upload ??
Click to expand...
Click to collapse
I recently bootloader unlocked then bricked the tcl a509dl hahaha was wondering if anybody could make a dump for me? I would be so very appreciative!
r1pp3d2 said:
I recently bootloader unlocked then bricked the tcl a509dl hahaha was wondering if anybody could make a dump for me? I would be so very appreciative!
Click to expand...
Click to collapse
I'll even teamview with somebody and use unlocktool to make the backup.
r1pp3d2 said:
I'll even teamview with somebody and use unlocktool to make the backup.
Click to expand...
Click to collapse
Following . Still need the stock firmware or dumps
Bahh... lame, I'm still in need of firmware/dump. Bout to go buy another one just to get it. lol .. they did have this phone at dollar general, I think its like 39$ .and the chick that's usually working gave me a discount, so the last one for $20. I think I have myself sufficiently talked into it now. If i do buy another, I will upload it for you guys.
iamx51 said:
Bahh... lame, I'm still in need of firmware/dump. Bout to go buy another one just to get it. lol .. they did have this phone at dollar general, I think its like 39$ .and the chick that's usually working gave me a discount, so the last one for $20. I think I have myself sufficiently talked into it now. If i do buy another, I will upload it for you guys.
Click to expand...
Click to collapse
Man, if you get another one I would love a backup from it.
r1pp3d2 said:
Man, if you get another one I would love a backup from it.
Click to expand...
Click to collapse
I have succeeded in getting the one I have already to allow me to do another dump, but it only boots to the bootloader says the dm-verity corruption crap, then reboots itself.c
If I remember correctly, this began after flashing a Magisk patched boot.img .. it is possible I did something else, but pretty sure that's what happened. messing with it now, will start the dumps before I pass out
iamx51 said:
I have succeeded in getting the one I have already to allow me to do another dump, but it only boots to the bootloader says the dm-verity corruption crap, then reboots itself.c
If I remember correctly, this began after flashing a Magisk patched boot.img .. it is possible I did something else, but pretty sure that's what happened. messing with it now, will start the dumps before I pass out
Click to expand...
Click to collapse
I'm pretty sure that's what screwed mine up too. But mine won't even come on now but I'm still able to connect to the chip to flash.
iamx51 said:
I have succeeded in getting the one I have already to allow me to do another dump, but it only boots to the bootloader says the dm-verity corruption crap, then reboots itself.c
If I remember correctly, this began after flashing a Magisk patched boot.img .. it is possible I did something else, but pretty sure that's what happened. messing with it now, will start the dumps before I pass out
Click to expand...
Click to collapse
any chance i could try that dump that you have?
iamx51 said:
Woo thank you for the info ! Unlocked and magisk rooted. Do we have twrp for this device on xda?
Click to expand...
Click to collapse
For clarification, are you stating that you have unlocked the bootloader and rooted the TCL A3 (A509DL) branded by TracFone Wireless. If so, as far as I know, there is a $1,700 cash bounty up for the first person to OEM unlock and/or root the A509DL.
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with