Hi All….received the 4.4.2 download this morning on my RMHD and ran through the install. At reboot the phone got stuck on the Red Moto logo… I let it sit for nearly 45 minutes, assuming it was doing its thing in the background. But at that point I figured it was safe to assume something got hosed. I rebooted back into recovery and did a factory reset. That wound up making things worse…now am in a boot loop between the logo and the Android triage guy (recovery)….
Phone was rooted and locked. And I am complete understanding that I was losing root with this OTA. Been reading all posts in here….please ‘flog’ me if I missed something.
With that said…I have two questions on recovering the device.
1) Can I simply download and copy one of the JB images from the Motorola Firmware site to my SD card and install via recovery (since my recovery appears to be OK)?
2) Or should I/need I follow procedures using RSDLite? And recover this way?
Any comments are appreciated!
Thanks
Doug
Never mind. iBolski's thread "Official KK OTA for 9.30.1 (XT926) users - please read" in the general forum looks like it might do the trick for me...and I won't be able to go to a previous (JB) Android version. This looks easy enough.
I have the same issue except I'm in need of a .zip or set of files for the modem firmware that I need to flash in 4.4.2 183.x.x Stock because I tried to downgrade to 9.30.1 jb and the firmware and the modem downgraded. Could someone create a package I can flash in stock recovery to restore my Droid Razr Maxx HD to to 4.4.2 183.x.x
I'm currently using the Droid Razr Maxx HD 9.18.94.XT926 and I'm trying to download the new KitKat OTA, but it's failing because I rooted my phone. I've been searching, and I'm not completely sure how to go about fixing this, if I even can. I have a locked bootloader if it makes any difference. To be honest, I feel silly for not being able to figure this out myself, but I really don't want to accidentally brick my phone. Turns out I know just enough to be dangerous. :crying:
Any help would be appreciated.
Instructions here for locked and unlocked bootloader. Also can't install the OTA with root. Has to be unmodified stock with stock recovery.
http://forum.xda-developers.com/showthread.php?t=2749157&page=6
skipnyip said:
I'm currently using the Droid Razr Maxx HD 9.18.94.XT926 and I'm trying to download the new KitKat OTA, but it's failing because I rooted my phone. I've been searching, and I'm not completely sure how to go about fixing this, if I even can. I have a locked bootloader if it makes any difference. To be honest, I feel silly for not being able to figure this out myself, but I really don't want to accidentally brick my phone. Turns out I know just enough to be dangerous. :crying:
Any help would be appreciated.
Click to expand...
Click to collapse
yujikaido79 said:
Instructions here for locked and unlocked bootloader. Also can't install the OTA with root. Has to be unmodified stock with stock recovery.
http://forum.xda-developers.com/showthread.php?t=2749157&page=6
Click to expand...
Click to collapse
OK, I figured being root was the problem. So now for my next question, how do I flash a stock ROM? I tried using the RDS Lite but I couldn't get my phone to show up. I also wasn't sure which file to use from http://sbf.droid-developers.org/phone.php?device=5 or if that mattered.
Here you go, you have to flash the stock rom, YOU will lose root.
Send me a pm (LOL i can't share links here hah i'm newbie), with the instructions that i followed, i'm right now on kit kat
House of Moto setup
please understand, I have a unlocked bootloader, so please take caution and read up on things before attempting.
Here I set House of moto up for XT926 it includes everything you should need to return to stock. I selected option #1
Of course you need the correct Motorola drivers installed for your phone.
More info on house of moto here:
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/
My personal setup of House of moto setup for XT926 9.30.1 stock
https://drive.google.com/file/d/0B5FXi3o099wtS3c2R0pVWmVWV2c/edit?usp=sharing
I used house of moto to restore stock 9.30.1 then as the instructions from the link I post in a previous posted from iBolski I put the downloaded OTA Kit kat update for the 9.30.1 on my external sd card. found here
http://www.drdevs.com/devs/livinginkaos/misc/xt926update/Blur_Version.9.30.1.XT926.Verizon.en.US.zip
I then setup my phone up before updating, then ran stock recovery. I got the andy with red exclamation mark, held down vol+ and vol- down for a second then got menu. Selected zip from external sd. It verified things, installed new recovery then I went back to recovery after restart.
This time at the andy with red exclamation I pushed, held down vol+ then pwr button for a second. It then entered the menu, selected OTA zip again. It installed, I then finally rebooted and had kitkat running.
skipnyip said:
OK, I figured being root was the problem. So now for my next question, how do I flash a stock ROM? I tried using the RDS Lite but I couldn't get my phone to show up. I also wasn't sure which file to use from http://sbf.droid-developers.org/phone.php?device=5 or if that mattered.
Click to expand...
Click to collapse
yujikaido79 said:
please understand, I have a unlocked bootloader, so please take caution and read up on things before attempting.
Here I set House of moto up for XT926 it includes everything you should need to return to stock. I selected option #1
Of course you need the correct Motorola drivers installed for your phone.
More info on house of moto here:
Can't even quote links yet.
My personal setup of House of moto setup for XT926 9.30.1 stock
Can't even quote links yet.
I used house of moto to restore stock 9.30.1 then as the instructions from the link I post in a previous posted from iBolski I put the downloaded OTA Kit kat update for the 9.30.1 on my external sd card. found here
Can't even quote links yet.
I then setup my phone up before updating, then ran stock recovery. I got the andy with red exclamation mark, held down vol+ and vol- down for a second then got menu. Selected zip from external sd. It verified things, installed new recovery then I went back to recovery after restart.
This time at the andy with red exclamation I pushed, held down vol+ then pwr button for a second. It then entered the menu, selected OTA zip again. It installed, I then finally rebooted and had kitkat running.
Click to expand...
Click to collapse
Thank you very much. Your instructions and file were extremely helpful. I'm now the happy owner of KitKat. For anyone else, reading, after I did everything and updated to KitKat, I had to factory reset my phone again to solve a problem with the Play Store, which worked with no problem.
I am currently running 4.4.4 but I want to go back to 4.2.2 stock rom that came with the phone and I want to root it. My bootloader is unlocked. And I did a recovery and wiped the phone within Android and it just went back to 4.4.4 not 4.2.2 like it did before. I went to fastboot and tried to go into recovery and wipe the cache but the phone just rebooted. I was able to wipe the cache before...maybe I did something wrong...I am very new to this and have downloaded so much stuff to do this but im sooooooo lost
Also Fastboot says that device is UNLOCKED, Status Code 3
Knight71 said:
I am currently running 4.4.4 but I want to go back to 4.2.2 stock rom that came with the phone and I want to root it. My bootloader is unlocked. And I did a recovery and wiped the phone within Android and it just went back to 4.4.4 not 4.2.2 like it did before. I went to fastboot and tried to go into recovery and wipe the cache but the phone just rebooted. I was able to wipe the cache before...maybe I did something wrong...I am very new to this and have downloaded so much stuff to do this but im sooooooo lost
Click to expand...
Click to collapse
factory resetting and wiping does nothing but remove data.
to get back to an older version, you will need to get the factory firmware file and flash it to the phone with rsd lite (tutorials can be found through google). afterwards, find a custom recovery that is compatible with the version you installed, install it, then grab the superuser flashable zip and flash in recovery to get your root back.
Sorry it took me so long to reply back. I drive truck OTR and I put in some long days. Ok I have some time to get this down and understood I will be going for my hometime at the end of this month for about 4 days because my phone is the only way that I can get online out here.
So I have a XT1080 Dev Ed. And I have a copy of a factory image from Motorola for my phone TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_1FF.xml.zip. Now how do I flash it do I have to unzip it or put it in a folder or??? And also (custom recovery that is compatible with the version you installed) do you mean using TWRP. Also what does Status code 3 mean and do I have to turn of Write Protection and if so how.
I am so sorry for being a noob at all of this. My old phone was a Droid Global 2. It was ok until it got old and unresponsive I used FoxFi to get online while I was out on the road. Then I decided to go and get me a new phone and I hear about the Droid Maxx and the awesome battery life on it so I decided to get it...But I had to Pay full price for it. 650 plus 50 for tax 700 total. The reason behind that is that I have unlimited data and I did not want to lose it.
Knight71 said:
Sorry it took me so long to reply back. I drive truck OTR and I put in some long days. Ok I have some time to get this down and understood I will be going for my hometime at the end of this month for about 4 days because my phone is the only way that I can get online out here.
So I have a XT1080 Dev Ed. And I have a copy of a factory image from Motorola for my phone TMO_RETAIL_XT1053_4.2.2-13.9.0Q2.X-116-X-17-57_MR1_1FF.xml.zip. Now how do I flash it do I have to unzip it or put it in a folder or??? And also (custom recovery that is compatible with the version you installed) do you mean using TWRP. Also what does Status code 3 mean and do I have to turn of Write Protection and if so how.
I am so sorry for being a noob at all of this. My old phone was a Droid Global 2. It was ok until it got old and unresponsive I used FoxFi to get online while I was out on the road. Then I decided to go and get me a new phone and I hear about the Droid Maxx and the awesome battery life on it so I decided to get it...But I had to Pay full price for it. 650 plus 50 for tax 700 total. The reason behind that is that I have unlimited data and I did not want to lose it.
Click to expand...
Click to collapse
unzip the factory file to a folder, inside there is a "xml" file, that is the target file you load into rsd lite.
before you start with rsd you will likely have to edit the xml first. right click it and choose edit. you are looking for any lines that contain "getvar". if you see that, delete the hole line from end to end (may be more than 1), then close and save when prompted.
now you can flash with rsd as usual.
yes twrp or cwm
status code 3 just means that the bootloader is unlocked.
as far as i know that should be all there is to it, i dont have this device so im just stating general moto flash procedures. if you found something about write protection that im not aware of, post a link and ill have a look at it.
here is the su zip you will need to install root after you install twrp or cwm http://www.mediafire.com/download/nwxoj8b3k1u8xtv/UPDATE-SuperSU-v2.01.zip just flash as is in recovery.
btw, i have unlimited data too
Got to love Verizon. My bill would be so expensive if I got on there 10GB Tier plan...I would go way over that. But the things that we do to keep it...like buying a 700 dollar phone...LOL
What is getvar and also how do I see the partitions on my phone?
Well I have to hit the road but will be back on here tonight.
Knight71 said:
Got to love Verizon. My bill would be so expensive if I got on there 10GB Tier plan...I would go way over that. But the things that we do to keep it...like buying a 700 dollar phone...LOL
What is getvar and also how do I see the partitions on my phone?
Well I have to hit the road but will be back on here tonight.
Click to expand...
Click to collapse
i dont know what getvar is really, but if its there (occasionally not) and you dont remove it, rsd will fail. its nothing needed to flash, thats all i know.
not sure how you would look at the partitions. you can wipe them in recovery, but you really dont want to mess with anything you dont understand. if you wipe the wrong thing, you will be in big trouble, and a factory file cant fix it.
Ok...I downloaded the files. I did not know if there is more then one partition on my phone or not. I have never done this on a phone before...Its a learning curve for me. I cant do this now it will have to wait until I get home so that way I can get online and you can walk me threw all of the steps and commands I need to send to my phone.
Knight71 said:
Ok...I downloaded the files. I did not know if there is more then one partition on my phone or not. I have never done this on a phone before...Its a learning curve for me. I cant do this now it will have to wait until I get home so that way I can get online and you can walk me threw all of the steps and commands I need to send to my phone.
Click to expand...
Click to collapse
In the future, please quote me or I may miss your post like I just did.
Thanks
Sent from my G2 running SlimKat
Last night i was unlocking the bootloader and it worked but i am now stuck in the TWRP menu and cannot do anything. I have tried to factory reset and nothing works. can someone please help me restore my phone to stock?
hodorprime said:
Last night i was unlocking the bootloader and it worked but i am now stuck in the TWRP menu and cannot do anything. I have tried to factory reset and nothing works. can someone please help me restore my phone to stock?
Click to expand...
Click to collapse
I did this on a OnePlus this am, so I wonder if it would work for a G3 as well? Hopefully someone with better know how will stop by.
Perhaps consider entering fast boot with your phone, on your PC use adp along with the full ROM version you wish to 'return to'. Unzip the ROM into the directory where adp is. Use the adp command to make sure your device is seen, of so you should be good.
There is a flash all .bat file that will flash all the necessary files, one at a time, and you can reboot from there. I'm in-between patients, so can not look up the link right now.
Remember, the above was for a OnePlus. Since they are both Android, I'm hoping someone will confirm this will work on a G3, as well.
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
I know more about Motorola Droid phones. This is phone is new to me. I did do a lot of research out there and mainly on XDA. I have the option to return the phone for a full refund. I would like to see if I can fix the phone before hand. I have till this weekend to send it back.
Claps1775 said:
I bought a new Brigadier off ebay. Phone is new and never used. The build date was July 2014 and KK 4.4.2. I should have paid more attention to the numbers. After the KK update my phone boots up but does not show anything after the Kyocera screen. It is black with the back light.
This is what I did. I put my SIM card in the phone to check that I can activate it. Then while I was testing out the phone. It downloaded the first update. I do not remember what the number is. The phone had never been used. It was new. I might be able to look it up for update history on big reds site. I did not do the do the update. After seeing it was done. I turned it off and put the SIM card backing the Turbo. After doing some research on rooting. I found that Kingroot (5.0.4) is best, then found this app I can use to remove Kingroot. Last night I was playing more with the phone and then rooted it too. I rebooted it, hotspot my turbo, downloaded root checker, confirmed root, then undated. Phone is at 80% life. Phone shut off and then I let it do its thing. When I came back, the screen is black with the back light on only. I can touch the screen and feel/hear the vibration. I can soft boot, hard boot, and reboot into stock recovery. I did a factory wipe after I read in how to boot stock recovery. Yes, did nothing. I do know that KK updates can kill your phone. My Droid HD maxx is dead. On that phone, the led light lights green up and the computer does make a sound when connected but does not show it. I have no idea if this has a rsd lite and file to flash. I did not change anything in the system at all. I did not think that Kingroot would mess with my phone if I did the ota. I would then buy this app and remove it. I was waiting for internet to be installed today to further mess with my phone before using it. I do not know how to pull info off my phone.
Click to expand...
Click to collapse
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The update you did was a stock update, correct?
You said the device was rooted and then you did the update, correct?
That's where you screwed up, you can't do stock updates on a rooted device, you have to remove root, have stock recovery and have an unmodified system partition before doing the update.
You should have done the update and THEN rooted the device.
Now just do a Google search for:
"How to unbrick (your model number)"
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yes and yes. Okay. I know with droids when I was bootloader locked and rooted. I was fine updating. There was a change on loosing root. It's all about learning. I will try to find out how to unblock my phone. Thank you for the response.
Have you came across the ota .IMG file?
I was able to power my phone off. I connected the phone to my computer, installed the software, and tried the repair part. Failed on downloading. Version on my phone is 1.102VZ.
I found more info on xda refuring to the http://4pda.ru/forum/index.php?showtopic=597313&st=3680 site. I am not able to do anything with my phone now. Cannot get it to boot in recovery or even have my pc see it. The verizon apk sees it where I can still try to repair or update. That is it. I am going to send it back for a full refund and be done with this phone. Cannot spend weeks trying to fix this right now. Thanks all for the help.
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
I was able to flash the Rom_5.1.1_3153LR_Modem_3153LR_E6782 and my phone booted up and went into the optimizing but it is in Russian. I am further than I was. Need to find out if this is changeable to English and it all works. Yes, I do know that I will not flash anything than 5.0 now since the bootloader is locked or it can be unlocked with a code. Phone is up and running. I need a 5.1.1 US now.
It is not in Russian. It is in vietnamese. But I still need a clean 5.0 full rom.
Claps1775 said:
Update. I got my phone into Fastboot. I was able to get phone into twrp recovery. How ever, I am not able to find a img I can flash to my phone then I will be able to use my phone. Ones I have found are twrp back ups that I have no clue how to flash. I downloaded Rom_5.1.1_3153LR_Modem_3153LR_E6782 and I hope to see if I can flash it or not in twrp. I still do not understand Android_SDK and how to use it. I am not sure if I can use twrp recovery from the Kyocera Brigadier E6782 Toolkit v1.2 I downloaded from the http://4pda.ru/forum/index.php?showtopic=597313&st=620#entry35662165 or not. All I am doing now is trying and seeing what happens. If anyone knows more please share.
Click to expand...
Click to collapse
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
You can use the TWRP backups by choosing the restore option in TWRP then selecting the backup file and it will restore the data in the file to your device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I will try that. I have to get it into fastboot and that can take a few tries. The firmware I have on it has no verizon apps. It is a mod by someone. I am going to try original firmware 5.1.1 firmware. Downloading right now. it is a .rar file. Making head way witch is good. I am learning for sure.
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Claps1775 said:
I got into fastboot mode. I tried to go into twrp using the Kyocera Brigadier E6782 Toolkit v1.2 as I did before. Now, I am stuck at the Android screen and it will not go into twrp. Ahh.
Click to expand...
Click to collapse
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
That's because of your now locked bootloader, can't use TWRP with locked bootloader.
It's a little late now, you need to slow down, if you had done some searching to see how to use TWRP backups(the information is literally everywhere in every device forum here, it works the same for all devices), you would have been able to restore one of those backups, you'd have the device fixed and you wouldn't have a locked bootloader, that bootloader limits your options now, it leaves you only the option of finding the correct stock firmware.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Claps1775 said:
I never knew it was unlock. On the Android screen it had a 1 at the top left corner and it is still there. I am trying to find the correct firmware and flash it. I am able to see my phone in the adb file I used to flash twrp on my Droids. I have done a lot of research and and the 4pda.ru site. I am sent a lot of pms out to XDA memebers and got nothing back. I have posted a lot and hope someone would replay. I am trying trust me. I flash the wrong one. If I brink the phone, O well. All I can say is I am not trying to give up. Not sure if I can flash a rom or a twrp back up in adb or not. I would like to sit and read up on all of this. Then I could have a better understanding and then may play more.
How can flashing the Rom_5.1.1_3153LR_Modem_3153LR_E6782 even lock the bootloader? Eventhing I read talked about it being locked. It says in the box, Failed (remote: bootimage: incomplete or not signed) when I try to boot it into twrp.
Click to expand...
Click to collapse
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
It locks the bootloader because when you flash the Firmware it upgrades to a different bootloader, one that is locked, it's coded into the firmware, it is intended to verify software signatures at boot, if the signature isn't what it's looking for it won't allow the software to load. Your TWRP, for example won't boot because it doesn't have the right signature, only your stock firmware has the right signature and there isn't a way to fake it. Your only chance of using TWRP is if your bootloader can be unlocked, not all bootloaders can be unlocked. It's a security measure installed by the manufacturer or your carrier to prevent flashing and modding the device, it's pretty effective and has become very common on a lot of devices since KitKat. It was implemented because they got tired of replacing devices due to the user modifying them and screwing them up, modified devices technically void the warranty but if screwed up enough they can't tell it has been modified, thus, they've been replacing devices that they weren't obligated to replace, they know this and are trying to put a stop to it.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Claps1775 said:
I messed up a great phone I was looking forward of using. I thought I had it all lined up. I read a lot and thought I understood things. Can it befixed? By Kyocera only I say. I wanted on 5.0 is while I flashed that rom. I did not know it was a custom one. I truly feel bad that I messed up a great phone. I am going to stick with Motorola Droids and HTC for me wife. I am up very late trying to figure this all out. I am going to stick with things I know even though I love a challenge and learning. Thank you for the help, yes, I should have slowed down but everything was going great. Live and learn.
Click to expand...
Click to collapse
When some, lose some.
For future reference, when you want to update or modify a device, try doing some research into what NOT to do or what can go wrong with that particular device and how to fix it if it does BEFORE you focus on what CAN be done on that device and before you actually do anything to the device. Cover the bases, ask questions, search for issues others might have had when they modified their device.
Remember, just because something is available for that device, doesn't mean you can use it. Things change from android version to android version and this stock firmware to that stock firmware for a device, such as whether the bootloader is locked or unlocked, among other possible differences that can turn things into a train wreck.
Android devices are all different and are not all done the same. What and how it is done on "this" device is not the same on "that" device.
Sent from my SM-S903VL using Tapatalk