Related
:cyclops:hi guys, first of all thank you because you have saved me many times in the past just by reading through the forums. but this time
nothing seems to help me, i have a htc one m8 from sprint, and i tried to root it and install a custom room. And i did rooted now my device
shows tempered and bootloader is unlocked. I used twrp for the custom recovery later i tried to install android revolution one 4.0
and did not work but not only that i erase the partition of the phone so i soft bricked and my phone end up stuck on the boot loader not even
twrp will work :crying:and i try to repair the partition by using some comands that i found, but my phone was not getting recognized by adb just fastboot.
After a day i try a different custom recovery philz. and that one worked so i was able to enter to recovery, and i don't know why but when im inside the recovery my phone gets recognize by adb. I try to repair the partition, but since i have to grant access on the phone is not able to finish. so i tried to install
different rooms such as viper, badseed and it goes through the set up, but when it finish it just gets stuck on the boot loader again. I been trying
to install the stock room but i haven't been able to find it, i found a link in many different forums but the links are broken i been dealing with this
issue for over 5 days and don't know what to do. i will really apreciate if someone cuold help me please forgive me if you don't understand me but
english is not my native lenguage, so i don't speak it very well. also i'm a noob on rooting so i may not know a lot by the way my phone is s-on. help will be
really appreciate.
If you are S-On, when flashing a rom, it will not be able to automatically flash the kernel (boot.img) unless it specifically states in the OP it does by the developers. Most of the time, you'll just need to extract the boot.img and place it in the folder you have fastboot, then when connected in bootloader / fastboot mode run this : fastboot flash boot boot.img
after you flash the rom. Just boot into it right after, flash, and the just type : fastboot reboot
Should be good to go. FYI : adb isn't intended to work in bootloader and fastboot doesn't work in recovery. Nothing wrong there.
Sent from over there...
es0tericcha0s said:
If you are S-On, when flashing a rom, it will not be able to automatically flash the kernel (boot.img) unless it specifically states in the OP it does by the developers. Most of the time, you'll just need to extract the boot.img and place it in the folder you have fastboot, then when connected in bootloader / fastboot mode run this : fastboot flash boot boot.img
after you flash the rom. Just boot into it right after, flash, and the just type : fastboot reboot
Should be good to go. FYI : adb isn't intended to work in bootloader and fastboot doesn't work in recovery. Nothing wrong there.
Sent from over there...
Click to expand...
Click to collapse
thank for the help and i did as you said i install viper it finish a soon as it finished the phone reboot and went to bootloader i extract the boot.img from the zip and put it on the fastboot folder flash it and it said okay then i reboot the device and again just got stock on the bootloader im going to try to install android revolution and do the same thing but i almost sure is going to do the same thing. any other advice that you can provide me i will really appreciate it
and thanks again for the help.
update
just and update i did try also with android revolution and still no luck :crying:any help will be really appreciated:cyclops:
Can you post the link to the roms you are trying to load? I'm wondering if you aren't try to flash ones not for the Sprint M8? I don't see the ARHD rom in the forum for your phone...
es0tericcha0s said:
Can you post the link to the roms you are trying to load? I'm wondering if you aren't try to flash ones not for the Sprint M8? I don't see the ARHD rom in the forum for your phone...
Click to expand...
Click to collapse
thanks for the help first of all i have try this ones
ViperOne_6.0.0
Bad_Boyz_Sprint_ONE_KitKat_v1.2
BadSeed_Sixth_Sense_RLS2.1
Sprint_M8_1.12.651.17_system_dump
SENSE_STOCK_ROOTED_VZW_M8
Android_Revolution_HD-One_M8_4.0_ART
this are the ones, thank for the help again and i soon as we go through this im going to give you a donation for the big help
homar_80 said:
thanks for the help first of all i have try this ones
ViperOne_6.0.0
Bad_Boyz_Sprint_ONE_KitKat_v1.2
BadSeed_Sixth_Sense_RLS2.1
Sprint_M8_1.12.651.17_system_dump
SENSE_STOCK_ROOTED_VZW_M8
Android_Revolution_HD-One_M8_4.0_ART
this are the ones, thank for the help again and i soon as we go through this im going to give you a donation for the big help
Click to expand...
Click to collapse
Well, I definitely see a couple issues with that list...
The Viper 6.0.0 should be this one: http://forum.xda-developers.com/showthread.php?t=2334294 Which is for the International M7.
The Bad Boyz rom you posted should be the one from here: http://forum.xda-developers.com/showthread.php?t=2635051 - This is for the M7 version.
The BadSeed rom should be the one posted here: http://forum.xda-developers.com/showthread.php?t=2694471 - Also for the M7 (hence the M8 *PORT* in the title thread.
Now, HTC was stupid for giving the new phone the same name, I'll give you that, and XDA doesn't have it set to really filter well between the 2 forums, BUT stuff like the date posted could have been a give-a-way as well. But honest mistakes for sure. So, how to fix from here since your partitions are probably thoroughly hosed...? Hmm. Since I don't think there is an official Sprint RUU, that will be tricky. You will most likely need to get a hold of a very experienced HTC dev like the one's whose roms you were trying to use. The Viper, Bad Boyz, and BadSeed dev teams are all very good at most everything HTC. Another option is the developer : Captain_Throwback. He is very knowledgeable about HTCs from top to bottom and seems to be pretty helpful. Your casual helper will most likely not be able to provide as detailed help as you would need in this situation.
The forums you want to hang out in for your phone are here: http://forum.xda-developers.com/sprint-htc-one-m8
es0tericcha0s said:
Well, I definitely see a couple issues with that list...
The Viper 6.0.0 should be this one: http://forum.xda-developers.com/showthread.php?t=2334294 Which is for the International M7.
The Bad Boyz rom you posted should be the one from here: http://forum.xda-developers.com/showthread.php?t=2635051 - This is for the M7 version.
The BadSeed rom should be the one posted here: http://forum.xda-developers.com/showthread.php?t=2694471 - Also for the M7 (hence the M8 *PORT* in the title thread.
Now, HTC was stupid for giving the new phone the same name, I'll give you that, and XDA doesn't have it set to really filter well between the 2 forums, BUT stuff like the date posted could have been a give-a-way as well. But honest mistakes for sure. So, how to fix from here since your partitions are probably thoroughly hosed...? Hmm. Since I don't think there is an official Sprint RUU, that will be tricky. You will most likely need to get a hold of a very experienced HTC dev like the one's whose roms you were trying to use. The Viper, Bad Boyz, and BadSeed dev teams are all very good at most everything HTC. Another option is the developer : Captain_Throwback. He is very knowledgeable about HTCs from top to bottom and seems to be pretty helpful. Your casual helper will most likely not be able to provide as detailed help as you would need in this situation.
The forums you want to hang out in for your phone are here: http://forum.xda-developers.com/sprint-htc-one-m8
Click to expand...
Click to collapse
thanks so much for the help im learning a lot like what is a RUU and as you said i try to look for one no luch anyhow i have a doom question how do i get a contact with them how can i get the help from the ones that you mention im sorry but so far i been using xda to read through the forums this is actually my first time posting a problem i will really appreciate the help thank you.
homar_80 said:
thanks so much for the help im learning a lot like what is a RUU and as you said i try to look for one no luch anyhow i have a doom question how do i get a contact with them how can i get the help from the ones that you mention im sorry but so far i been using xda to read through the forums this is actually my first time posting a problem i will really appreciate the help thank you.
Click to expand...
Click to collapse
1 of 2 ways : post on a thread they have up, or click on their name on the left pane of the forum thread and it should give you options to Private Message the member. Keep in mind, many developers are busy people and some of them just ignore their PMs because they get so many for simple questions. Yours is certainly not gonna be the easiest fix. I would suggest to maybe start here: http://forum.xda-developers.com/showthread.php?t=2696652
es0tericcha0s said:
1 of 2 ways : post on a thread they have up, or click on their name on the left pane of the forum thread and it should give you options to Private Message the member. Keep in mind, many developers are busy people and some of them just ignore their PMs because they get so many for simple questions. Yours is certainly not gonna be the easiest fix. I would suggest to maybe start here: http://forum.xda-developers.com/showthread.php?t=2696652
Click to expand...
Click to collapse
thank you so much i'll do that, i really appreciate your help and your time
homar_80 said:
thank you so much i'll do that, i really appreciate your help and your time
Click to expand...
Click to collapse
No problem! Don't let this scare you away from trying to mod your phone later on. Just use this as a learning experience about the importance of reading. Lots.
hay
+D
es0tericcha0s said:
No problem! Don't let this scare you away from trying to mod your phone later on. Just use this as a learning experience about the importance of reading. Lots.
Click to expand...
Click to collapse
thank you for everything and i will keep trying also i have another htc one but the first generations i will mod it as well as soon as im done with this one jejeje
and believe me that i been reading for day trying to find a solution to my problem but hopefully soon with some help can be able to do it and if you want i can post and update in here of how finally i was able to fix it... thanks
First off, this should be posted in the Sprint M8 Q&A forum.
Next, I assume you have a stock nandroid, as that's the first thing everyone should do after getting a custom recovery installed on the device. So start by restoring that. If for some reason you don't have that, I believe there's one floating around in the "Stock ROM or any" thread in Sprint M8 General or Q&A.
Once you can boot up the device, you should be good to proceed to S-OFF and flash only ROMs specified for the Sprint M8 variant.
My pleasure. It's how I like to give back to the community. I have a ridiculous amount of experience with everything root, recovery, rom, mods, themes, apps, etc related after modding 100s of phones and tablets, but these type of issues require the next tier of experience when you're getting into semi uncharted territory due to how new the device is and that HTC hasn't released the official update utility for it. But yea, you should post back, just in case another member runs into the same problem and you can help point them in the right direction.
Captain_Throwback said:
First off, this should be posted in the Sprint M8 Q&A forum.
Next, I assume you have a stock nandroid, as that's the first thing everyone should do after getting a custom recovery installed on the device. So start by restoring that. If for some reason you don't have that, I believe there's one floating around in the "Stock ROM or any" thread in Sprint M8 General or Q&A.
Once you can boot up the device, you should be good to proceed to S-OFF and flash only ROMs specified for the Sprint M8 variant.
Click to expand...
Click to collapse
thanks for the quick help and yes i did create a back up of the phone but when i was trying to install the first custom room Android_Revolution_HD-One_M8_4.0_ART it ask me if i want to delete all data and i said yes. So my partitions of the phone i believe are screw up. I did look for Stock room i found many that were linking to the same file both the oex and deodex links were bronken and i haven't been able to find the one that i need that is kitkat 4.4.2 sprint. and i don't know what's next from were i am now.
homar_80 said:
thanks for the quick help and yes i did create a back up of the phone but when i was trying to install the first custom room Android_Revolution_HD-One_M8_4.0_ART it ask me if i want to delete all data and i said yes. So my partitions of the phone i believe are screw up. I did look for Stock room i found many that were linking to the same file both the oex and deodex links were bronken and i haven't been able to find the one that i need that is kitkat 4.4.2 sprint. and i don't know what's next from were i am now.
Click to expand...
Click to collapse
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
EDIT: http://forum.xda-developers.com/showthread.php?p=51624633
Captain_Throwback said:
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
Click to expand...
Click to collapse
He flashed 3 or 4 different roms that were for the M7 or not for his version of the M8. Pretty sure that the partitions are borked at this stage as properly flashing the correct M8 rom and fastboot flashing the boot.img has not gotten him out of trouble.
es0tericcha0s said:
He flashed 3 or 4 different roms that were for the M7 or not for his version of the M8. Pretty sure that the partitions are borked at this stage as properly flashing the correct M8 rom and fastboot flashing the boot.img has not gotten him out of trouble.
Click to expand...
Click to collapse
thanks i was looking for the words to explain that my English is really bad i apologize for that.
homar_80 said:
thanks i was looking for the words to explain that my English is really bad i apologize for that.
Click to expand...
Click to collapse
Did you see my post?
---------- Post added at 05:15 PM ---------- Previous post was at 05:11 PM ----------
Captain_Throwback said:
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
EDIT: http://forum.xda-developers.com/showthread.php?p=51624633
Click to expand...
Click to collapse
If restoring the above doesn't work, you can try this:
- Relock bootloader (fastboot oem lock)
- Download signed firmware zip from here. Flash via fastboot (fastboot oem rebootRUU, fastboot flash zip firmware.zip, fastboot reboot-bootloader)
- Unlock bootloader via HTCDev.
- Download TWRP Recovery from here and fastboot flash (fastboot flash recovery openrecovery-twrp-2.7.0.2-m8_whl.img)
- Download Stock Rooted ROM from here and flash via TWRP.
Dear Developers and Users
I have moto E xt1021 some time ago. Once it happen that my phone Android crashed then I successfully flashed back new kitkat 4.4.4.
My phone worked fine and even checked if there is any software updates, I think this was my mistake. Then I upgraded to Lollipop 5.0.2.
Also I installed CWM recovery but as a beginner, did not thought of backing up all my data, another mistake because all my data are gone now.
Every thing was fine for about one month. Suddenly, last week my phone starts freezing and not responding to any touch.
Well, the quick solution is re-start. But it never came back again to more than the Moto logo.
Depending on what I was reading since last week, I think my phone is brick now, hopefully soft, because the situation of my phone is as follows
Stops by Moto logo when pressing power on.
I can go to the Bootloader menu.
I can see my CWM-recovery menu. But from here I am not able to flash new ROM, Stock, or even recovery.
My phone is unlocked and rooted as far as I remember, I hope it is still.
and the most important part:
USB debugging mode WAS NOT ENABLED before it crashes and it still not enabled.
I installed on my PC SDK, fastboot and ADB tools, Motorola Drivers.
I have been trying for a week now several tens of threads but unfortunately never succeeded to bring it back working.
I don't care for my data now. Important to get alive.
I am sorry for the long thread. I tried to put all information needed and hope nothing is missing that clarify this problem. BTw, I bought my phone from Germany.
Any help or recommendation what to do would be highly appreciated, Especially with enabling the USB DEBUGGING MODE which I think is the key solution.
Thanks in advance
Sadam.
What about: http://forum.xda-developers.com/showthread.php?t=2755857
If you can boot your phone into fastboot mode you should be fine. Just follow the flashing tutorial.
Alternatively, if you can only get into cwm recovery there is an option in moto e android development to restore to android 5.
am2012 said:
What about: http://forum.xda-developers.com/showthread.php?t=2755857
If you can boot your phone into fastboot mode you should be fine. Just follow the flashing tutorial.
Alternatively, if you can only get into cwm recovery there is an option in moto e android development to restore to android 5.
Click to expand...
Click to collapse
Thanks for your answer am2012
I followed this tutorial and many other similar threads.
It gives me always the same error whenever I ran command with mfastboot.exe (I mean the whole bunch of mfastboot commands). Please check the error.jpg in the attachment. Maybe some one have seen such error and how to solve it.
Could be also something to do with the partition of my device ? If yes, Any suggestions are appreciated!
Thanks
SadamHazaimeh said:
Thanks for your answer am2012
I followed this tutorial and many other similar threads.
It gives me always the same error whenever I ran command with mfastboot.exe (I mean the whole bunch of mfastboot commands). Please check the error.jpg in the attachment. Maybe some one have seen such error and how to solve it.
Could be also something to do with the partition of my device ? If yes, Any suggestions are appreciated!
Thanks
Click to expand...
Click to collapse
So you can actually boot into cwm recovery not just bootloader?
Can you take a picture of your phone in recovery? I might have an idea.
I asked a friend and he said go to bootloader and flash 4.4.4 using adb. http://forum.xda-developers.com/showthread.php?t=2759495 You must flash 4.4.4, not earlier or phone will brick.
am2012 said:
I asked a friend and he said go to bootloader and flash 4.4.4 using adb. http://forum.xda-developers.com/showthread.php?t=2759495 You must flash 4.4.4, not earlier or phone will brick.
Click to expand...
Click to collapse
I tried it and again the same failure as in the first reply
I attached my bootloader menu and Recovery menus as well.
Thanks
SadamHazaimeh said:
I tried it and again the same failure as in the first reply
I attached my bootloader menu and Recovery menus as well.
Thanks
Click to expand...
Click to collapse
It's a little beyond me now. I have found this YouTube video: https://www.youtube.com/watch?v=pYjQePBRzhk
Let me know if it is any good?
If you search for the error codes there are lots of results on google.
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
Hello there, sorry for posting, this is literally my last resort.
So, here's the whole story. In my attempts to install a custom recovery mode(first TWRP) then I tried to follow this guide: Link is here of xda forum. So, my phone runs Fastboot and doesn't really have any stock recovery (just a factory settings window, which is now gone as well). So apparently after I entered these two commands into adb
fastboot oem unlock
fastboot format userdata
Click to expand...
Click to collapse
The first command unlocks the boot-loader and I thought that the second command would erase userdata, which is just photos and files, but apparently that second command has erased the whole rom + the factory settings window, that was on the phone.
So that's basically the story, now I am searching for a Stock ROM of the Flycat Optimum 5501, Android 5.1.
My phone is:
Flycat optimum 5501
Was running Android 5.1
If any information is required, I will provide. Please help and thank you for reading!
Alright development update. I've did like hell of a lot of digging, until it hit me to check the official Flycat website, so I went back and forth through the whole website right? And bam, I literally found 2 STOCK ROMS by going to this link.
I am still currently looking into ways to how to install this rom. If anyone could give advice onto how to install it using Fastboot, I would be thankful!
Update: So I found out that an application "Smart phone Flash tool" can flash your whole phone if you accidentally ****ed up. So I went to watch a few tutorials in youtube about that application and I managed to unbrick my phone. It works as it worked at the start. Welp I managed to fix it with pure research and dedication to this **** (I gotta get some beer)
At any case, for those of you who have the same phone and run into the problem. I hope that my updates will help ya. Sorry for the constant posting, my problem is fixed ^^
I do still wanna find a custom recovery image, that would work on this phone, so if anyone finds a way, please comment!