Related
I am wondering how easy it is to brick my Captivate. Also, how easy is it to brick the phone, with the only solution being to use a JIG?
Is the only way to brick if you do something stupid? If you follow all instructions (flash to stock, etc.) is it even possible to brick it? I've upgraded my phone to 2.2 using Kies; does the fact that I've upgraded once make it muc less likely to fail and brick later?
I'm wondering this because all the ROM makers must flash constantly, so I'm thinking there must be a way to avoid bricks.
Thank you!
AmandeepG said:
I am wondering how easy it is to brick my Captivate. Also, how easy is it to brick the phone, with the only solution being to use a JIG?
Is the only way to brick if you do something stupid? If you follow all instructions (flash to stock, etc.) is it even possible to brick it? I've upgraded my phone to 2.2 using Kies; does the fact that I've upgraded once make it muc less likely to fail and brick later?
I'm wondering this because all the ROM makers must flash constantly, so I'm thinking there must be a way to avoid bricks.
Thank you!
Click to expand...
Click to collapse
Depends on your Captivate. In general, it's a bad idea to flash back to stock unless absolutely necessary. Bad Odin flashes are one of the biggest causes of bricked Captivates. Bad flashes through other methods (like CWM) usually leave you with boot problems, but working button combos for download mode. You should also check beforehand that your button combos work, since some Captivates are without them out of the box.
Also, wrong forum. This belongs in Q&A.
GGXtreme said:
Bad Odin flashes are one of the biggest causes of bricked Captivates.
Click to expand...
Click to collapse
Isn't the accepted way (as in the stickied thread) to always flash to stock?
GGXtreme said:
You should also check beforehand that your button combos work, since some Captivates are without them out of the box.
Click to expand...
Click to collapse
"Hold down both volume buttons and while holding them down plug the phone in." works for me
I have bricked my phone to the point of needing a jig 3 times now all because of odin. But the jig is 99 cents and is easy to use
sent from my captivate running a kitchen rom and hardcores 256hz k12n
kschumake83 said:
But the jig is 99 cents and is easy to use
Click to expand...
Click to collapse
Can you buy it, or do you have to make it from components?
Flashing back to stock is only needed when you have to, but no you do not have to flash to stock every time you flash a rom, a bad odin flash is usually the main cause in a bricked phone.. But as long as you can get to recovery or download mode, then its not bricked, you can usually get something flashed either way
existz said:
Flashing back to stock is only needed when you have to, but no you do not have to flash to stock every time you flash a rom, a bad odin flash is usually the main cause in a bricked phone.. But as long as you can get to recovery or download mode, then its not bricked, you can usually get something flashed either way
Click to expand...
Click to collapse
But the stickied thread says the exact opposite. I'm a little confused.
nbs11 said:
Here is the rule of thumb: if it does not specifically say anything about being able to not use ODIN in the original thread for the ROM you MUST you ODIN.
Click to expand...
Click to collapse
AmandeepG said:
But the stickied thread says the exact opposite. I'm a little confused.
Click to expand...
Click to collapse
Sometimes personal habit becomes the correct way to do something. For instance one teacher teaching how to count with pictures of apples and the other using oranges.
GGXtreme said:
Bad Odin flashes are one of the biggest causes of bricked Captivates. Bad flashes through other methods (like CWM) usually leave you with boot problems, but working button combos for download mode.
Click to expand...
Click to collapse
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
zelendel said:
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
Click to expand...
Click to collapse
Thanks! I'm gonna check if my Captivate has this 3 button recovery mode.
If it does, is the 3 button way just as effective as a JIG? And how effective is the 3 button and JIG at recovering from bricks (like I mean, how possible is it that they will not work)
AmandeepG said:
Can you buy it, or do you have to make it from components?
Click to expand...
Click to collapse
you can buy jigs online people sell for 20$ or so...but it's actually very simple to make and so cheap as well so buying one is slightly pointless. also, i have flashed too many roms i've lost track, my phone shutdown in the middle of an odin, etc etc, and i always manage to get out of it so i wouldn't be concerned. having 3button enabled helps tho
AmandeepG said:
Thanks! I'm gonna check if my Captivate has this 3 button recovery mode.
If it does, is the 3 button way just as effective as a JIG? And how effective is the 3 button and JIG at recovering from bricks (like I mean, how possible is it that they will not work)
Click to expand...
Click to collapse
I am guessing that you are concerned with bricking yours. You must be thinking about flashing a rom for the first time. I needed the jig yesterday for the first time. From what I understand, the jig method is almost a guarantee fir download mode, making the captivate nearly unbrickable. Can it be bricked... I am sure it can, but you are part of a community full of resources to keep you from doing so. You trepidation is not unique... I too was slow to flash my captivate. Now that I have, I have a phone that I love. I have been able to contribute to the community. And... I have a new found addiction.
Hi. My username is NunHugger and I am a flashaholic.
Sent from my SGH-I897 using XDA App
NunHugger said:
I am guessing that you are concerned with bricking yours. You must be thinking about flashing a rom for the first time.
Click to expand...
Click to collapse
You are completely right there!
I think I'll hold off doing my first flash until I can go out and get the parts for the jig, make and test it, so I can be sure nothing bad will happen
zelendel said:
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
Click to expand...
Click to collapse
Same here...corrupted data is corrupted data..and will cause problems...no matter how it gets loaded ...I've have been using Odin since I came to the Captivate..and is the only way I have been able to actually enjoy a new rom..A new rom...a fresh install..less problems for me.
Mac
A question about download mode:
I want to test if my captivate can get into download mode by the 3-button combo. However, I don't have any zips to update or anything to download or anything like that.
How do I enter download mode and then exit without making any modifications?
I thought I could just power the phone off, but in big letters it says "Do not power off target" (in videos I've watched).
AmandeepG said:
Isn't the accepted way (as in the stickied thread) to always flash to stock?
Click to expand...
Click to collapse
Accepted, yes.
Stupiud, yes.
You don't need anything to flash to get into DL mode
Just follow the instructions as it says and if it comes up you can just reboot the phone. Although you have to pull the battery. Although I've heard that holding just the Vol Up and Power for 10 secs also works. I've never tried it though
AmandeepG said:
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Click to expand...
Click to collapse
Depends on a lot of factors. It could be that your Captivate doesn't support flashing back to earlier than JH2 (JF6 one-click will brick), that your Captivate is already missing button combos (requires C3P0LOL's fixed Odin or AT&T's OTA JH7 update), a bad USB cable, problems with Windows, using the wrong USB port, etc. (all on top of user error). Lagfix won't affect Odin flashes.
AmandeepG said:
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Click to expand...
Click to collapse
I wouldn't say they are random. They are probably mostly caused by user error or some fault in the USB chain (port, cable, driver interactions). Whatever the root cause, from what I can see almost all bricks/semibricks are the result of using odin (I include cases such as where a cwm flash results in a boot loop and the user can recover because he used one-click and has no button combos).
I need the Stock Firmware version G900AUCU2AND3 So that I can flash back to stock. In the thread return to stock it has the previous version G900AUCU1ANCE. I get a error when trying to odin back (SW REV CHECK FAIL : [about]Fused 2 > Binary 1). So I am not sure how its done but need someone who has it do a dump or how ever its done to get it in a way that it can be flashed either by odin or in recovery... Any help will be appreciated... Thanks
i will need this too, i have my phone on at&t next and after a year i can trade it in, but if its custom os and stuff i cant return it, so i will need this too if i want to return to stock so i can upgrade to a new phone next year.
Bump: This is needed very badly. As I imagine many people had to take that bloat ware update. If anyone that has this firm ware has a problem and needs to restore back to stock. They won't be able to use the one that's listed in on this forum as its the older one, and now that there is Root. Its very likely this will happen daily that people will need it. I don't know exactly what soft bricked my phone so it can happen to anyone. My phone was fine until a reboot. Please, please, please. I'm begging everyone that has it. I asked Samsung and they wouldn't help. Next maybe going to AT&T store and having warranty claim done. I don't really want to find the out come of that.
I need this very badly as well. I rooted my phone and then tried to alter my screen density via an app I found on Google Play. It requested root, I granted the permission and then when the phone rebooted it hung on "Samsung Galaxy S5" splash screen and will no go any further. ODIN will not allow me to flash G900AUCU1ANCE firmware since I did the OTA update. If anyone could post up their G900AUCU2AND3, I would appreciate it very much.
kwikrat said:
I need this very badly as well. I rooted my phone and then tried to alter my screen density via an app I found on Google Play. It requested root, I granted the permission and then when the phone rebooted it hung on "Samsung Galaxy S5" splash screen and will no go any further. ODIN will not allow me to flash G900AUCU1ANCE firmware since I did the OTA update. If anyone could post up their G900AUCU2AND3, I would appreciate it very much.
Click to expand...
Click to collapse
I estimate we will get @ least One to two of these per-day until we get the files. Since we now have Root. It may take a bit as At&t version don't seem to have much for devs. Or ones that care to really help.(I'll probably get reamed for this. Sorry for you that help and for your time) I contacted At&t they told me they could not help but I could send my phone in for warranty exchange. Its that or go to BestBuy and they can flash it back. I don't have a Bestbuy Nearby.
Guys, check that post. Shortydoggg found a temporary fix for any soft bricks. It's for extreme cases. My phone is fine (apart from some deleted stock apps) so I'll hold off until i get some more info but if you cant boot at all, his method should come in handy.
http://forum.xda-developers.com/showthread.php?t=2785185&goto=newpost
+1 :highfive:
NotDavid said:
Guys, check that post. Shortydoggg found a temporary fix for any soft bricks. It's for extreme cases. My phone is fine (apart from some deleted stock apps) so I'll hold off until i get some more info but if you cant boot at all, his method should come in handy.
http://forum.xda-developers.com/showthread.php?t=2785185&goto=newpost
Click to expand...
Click to collapse
Thank you. The above link solved my problem. I am back up and running! At first data wasn't working other than wi-fi but I merely had to re-enter my APN that I got from here: http://forum.xda-developers.com/showthread.php?t=2746380 :good:
can you update to G900AUCU2AND3 after flashing this?
dave1977nj said:
can you update to G900AUCU2AND3 after flashing this?
Click to expand...
Click to collapse
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
pcidiot said:
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
Click to expand...
Click to collapse
Thanks!!! :good:
pcidiot said:
YUP, I did the AT&T update check and got it immediately afterwards. I instead of flashing every one separately and rebooting loaded the three files so minus the Bl file. I did not have the problems of having to reload APN this way.
Click to expand...
Click to collapse
A flash of the CSC file restores the APN after flashing the AP file, or flashing it together with the AP file, but it factory resets the phone. Flashing the AP file only is mostly for those who do not want a factory reset. But, a factory reset along with flashing only the AP file will indeed wipe the APN. I found all of that out through trial and error.
shortydoggg said:
A flash of the CSC file restores the APN after flashing the AP file, or flashing it together with the AP file, but it factory resets the phone. Flashing the AP file only is mostly for those who do not want a factory reset. But, a factory reset along with flashing only the AP file will indeed wipe the APN. I found all of that out through trial and error.
Click to expand...
Click to collapse
Thanks for your trials this will be useful to many.
pcidiot said:
Thanks for your trials this will be useful to many.
Click to expand...
Click to collapse
No problem.
dave1977nj said:
can you update to G900AUCU2AND3 after flashing this?
Click to expand...
Click to collapse
Yes do not root first, flash it then wait a few minutes then do a check for updates it will download the crap update with the yp yellow pages app,
then reboot and root
and take it away !!
pcidiot said:
Bump: This is needed very badly. As I imagine many people had to take that bloat ware update. If anyone that has this firm ware has a problem and needs to restore back to stock. They won't be able to use the one that's listed in on this forum as its the older one, and now that there is Root. Its very likely this will happen daily that people will need it. I don't know exactly what soft bricked my phone so it can happen to anyone. My phone was fine until a reboot. Please, please, please. I'm begging everyone that has it. I asked Samsung and they wouldn't help. Next maybe going to AT&T store and having warranty claim done. I don't really want to find the out come of that.
Click to expand...
Click to collapse
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Achilles5410 said:
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Click to expand...
Click to collapse
There should only be two boxes checked in odin thats f. reset time and auto reboot. Also Make sure you only check and load your firmware in the ap slot in odin. Now flash.
Achilles5410 said:
Same troubles here pcidiot!!!! soft bricked and nothing will load onto the phone. ODIN gives me the same kind of error as listed on the starting thread! I can get to recovery mode and Download (ODIN) mode on the phone but nothing wants to flash. Do we dump? Do we Erase Nand? CONFUSING!!! why is it so easy to bunk up a phone!
Click to expand...
Click to collapse
Are you following this guide?
http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1
shortydoggg said:
Are you following this guide?
http://forum.xda-developers.com/showpost.php?p=53454972&postcount=1
Click to expand...
Click to collapse
Yea I did thank you. Did it today and thanked the poster too.
Want to start over! Need help!
So I want to do whats written out in step 4 of shorttydogs thread but I don't want to mess up or brick my phone. My goal is to start over and go back to stock with bloatware and everything that is available on stock if I were to go AT&T and buy it today. Here is a little background on my phone. My phone is rooted and I do have safestrap (and busybox). I backed up everything on my microSD card. I also have the g900AUCU2AND3 firmware on my phone. In addition, I deleted some but not all AT&T bloatware, which I want back. Lastly, for some reason the "add call button" during my calls is missing and was replaced with a "record" button I think this was because of me playing around with xposed. I deleted xposed framework as well as wanam and tried everything to get the "add call button" back but I couldn't. Thus, I just want to go back to stock to fix all these issues. I just have a few questions before I proceed just to make sure I'm not doing anything wrong.
1) If I flash the AP, CP and CSC files will I achieve 100% stock with bloatware?
2) Will this return my "add call button"?
3) Is it as simple as just using odin 3.09 and flashing the AP, CP, and CSC files?
4) I also understand that this will take me back to G900AUCU1ANCE but will I be able to do an OTA do go to G900AUCU2AND3?
5) Is there anything else I need to know to prevent my phone from bricking!
Sorry for the long post but I am fairly new to this stuff and don't want mess anything up!
Hi community.
(I've searched without success!)
I've 'broken' my Xperia T. It was rooted and I used Titanium BackUp to 'merge updates to ROM'. Unfortunately the phoned locked up mid process and upon rebooting my phone is failing to boot. I *think its on Android 4.2.. I'd guess I've corrupted the ROM..
I'm afraid I'm unsure if my bootloader is unlocked or not, i rooted over a year ago and cannot remember what i did.
Upon boot I see the 'sony' name for a couple of seconds, it loops doing this and then sometimes I see the symbol that is its 'fix boot thing' that tries to fix the problem. But it never does. So it is stuck in a constant loop, never getting past the earliest part of the boot sequence.
I can't get into Recovery Mode.
What method can anyone suggest I try to recover this? To me as a noob there seem to be numerous recovery methods none of which i understand at this point. What I'd really love to hear is a suggested recovery method and then i can read up and try. As i stand I'm all a bit daunted of where to start.
Thanks for any help on a suggested recovery method. If my phone is beyond repair, that is fine.
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
istux said:
It seems your kernel is broken.
It doesn't exist android 4.2 for our device... so, what is your version? 4.1.2? 4.3? And which is your actual firmware?
This is important because if you flash the proper kernel, you can access to your system again.
If you have no idea, then flash a new clean stock firmware.
Take a look here: http://forum.xda-developers.com/showthread.php?t=2648320
For rooting and recovery, it will depend on which android version you choose.
For last android version 4.3, here is a quick tutorial: http://forum.xda-developers.com/showthread.php?t=2798411
Click to expand...
Click to collapse
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Watoh said:
Thanks mate that is very helpful.
I'm afraid i really don't know my firmware, build number or anything. All i know is is was an older version of Android 4.xxx If i had to guess i'd say 4.1.2.
If i can flash it to a stock firmware that is great! I'll run through this process see if i can get the 'flashtool' to communicate to my device.
:good:
Click to expand...
Click to collapse
You're welcome... and don't mess again with Titanium backup and tools like that... instead, once you've rooted, learn to use backup/restore of recovery... it's way better
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
WhiteNeo said:
I actually doubt its kernel related. More likely is a certain important system app has been wrongly replaced and is causing the problem.
As far as I know, Titanium Backup doesnt do anything to the kernel.
Click to expand...
Click to collapse
Yes, maybe you're right...
but the behaviour he reports about powering on and loops, is usually related to something wrong with the kernel.
In addition to this, he can't access to recovery anymore... and recovery is loaded before system. Why?
Or he means "recovery mode" as a lighter system mode (like windows for PC)... yes maybe he means this one... and not a recovery like CMW, etc...
He talks about "merging updates to ROM"... I actually don't know what he means exactly, I don't know how that titanium backup feature works, but if you update system files without updating the kernel, sometimes you can get bootloops because they don't match anymore.
At this point it's better he flash kernel+system together, that's why I suggested Flashtool ...and wiping all data too, is even better
istux once again thank you so much. It worked... on about the 30th time!
I would never have persevered without being given direct advice that this should fix my issue, so i'm very thankful.
I did have several issues getting it to work. For some unknown reason my Win 8.1 desktop refused to install the drivers required. It took me several attempts to realise the drivers were needed. I then switched to my Win 7 laptop and the drivers installed without issue.
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Watoh said:
But the main issue i was having was the power loop, I couldn't effectively switch off the phone. I had to let it the battery die entirely and then try, after about 20 attempts over 12 hours and several battery drains it suddenly sprang into life and started flashing. Its now as a factory reset.
Click to expand...
Click to collapse
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
istux said:
Why didn't you tell you weren't able to power off before?
If you get infinite bootloops, you have to push power+vol.up until it turns off.
You don't need to discharge the battery completely, because if kernel is actually corrupted you couldn't be able to recharge the phone anymore, because recharging process is managed by the kernel.
The risk to turn a bad situation into a nightmare is very high in these cases!! Be careful next time!!
Click to expand...
Click to collapse
To be honest I didn't actually know i was unable to power off until the instructions told me I had to and i tried without success!
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.
belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn
Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though
Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.
If you ever had loaded into recovery in temporary TWRP you'll note that even after formating /data/ and doing an advance wipe (selecting everything), then enter the file manager there is still a bunch of folders and some files throughout your device.
Is there a way to wipe out everything and start completely 100% fresh?
DO NOT DO THIS --- OR --- DO but do not cry about it
I have an answer to my question and it is as I suspected. The short and more official answer is, no. The longer answer is, yes, technically. -- But you should not try it unless you are 100% sure you can live without your phone (forever).
As it turns out no one had a full 100% flash for the whole device and its complete file system structure (except for Motorola). But as it turns out without a manufacturing cable it would be useless anyway. This is because part of your phone is protected and cannot be wiped clean and flashed so blindly... ie... Unlike your desktop computer. But if you're like me you have noticed some orphan files (a few logs).
Is it worth taking the risk just to clear some orphan files? Probably not. But since you do not have a manufacturing cable and technically, your phone can recover, what you can do is the following.
Do NOT use the TWRP installed on your phone. Rather use it in memory
Code:
sudo fastboot boot twrp-3.3.1-0-payton.img
Load TWRP and format DATA
Reboot, go to advance wipe, wipe everything.
Reboot to TWRP (again)
In TWRP via the terminal type in
HTML:
rm -r -f *
You will see a lot of things that cannot be deleted. This is because you do not have permission to do so. What little is removed will likely be restored after reboot from the master rom hidden somewhere on your phone which cannot be played with unless you have a manufacturing cable (so I am told). ---- If you have such a cable --- DO NOT DO THIS. --- If you suspect you have such a cable --- Do NOT do this. -- I did this with just my normal charging cable.
After you have run the command which will take forever. Tell TWRP to reboot to bootloader. You will now have a BLACK screen. This is where I panicked. I waited a while and long pressed down the power button (presumably turning off my device). Then I pressed down the power button and the lower volume button. -- Keep holding the buttons. -- It will take longer than you like but your phone will boot up. And low and behold everything that was in the master rom (chip?) has been restored and you will now see the bootloader screen (finally). Load TWRP and install your ROM of choice.
How many times have I done this successfully? 2x
Does this mean this is dependable? Unlikely
Do I recommend this? No.
Should you depend on this? No.
Are you taking a large gable? YES
Can this brick your device? YES, more than likely.
Should you do this if you have any doubts? NO.
Will you get any help if this goes wrong? NO.
So why did I do it? As I look to possibly upgrade my phone in the future I feel a little more daring and can afford to do so. lol
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
KrisM22 said:
you say "yes, technically", but I have yet to see someone get back to a fully operational stock. The best they can do is get to a mostly operational custom ROM. I (and a bunch of other folks here) would love to be proven wrong.
Click to expand...
Click to collapse
After performing this I installed only the official firmware. No additional ROM or GSI. The firmware itself includes the stock software.
A word of caution. --- I did this on 3 phones now. 2 work just fine. But 1 does not. The one that does not reports my IMEI as 0. This means it boots, it loads, it will play games and apps and update via Google Play Store, but it will never make a single phone call ever again. --- Food for thought.
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
MotoX4 said:
The world will never know. lol --- I'm a Linux user and their app doesn't seem to like Wine. I suppose I could set up a virtual machine with Windows and hope to connect through that. But I was once informed you really cannot do that via a virtual machine. Unless I was misinformed?! In any case, flashing the phone is not a problem. I can wipe it and reinstall any ROM or GSI at the moment. Or I can repeat my process too back to stock under a full wipe. The results appear to be the same.
I already have ordered a cheap Moto G7 from Google as a replacement. My current plan will be to find a very light (small), bare-bones ROM / GSI and install it onto this Moto X4. From there I'll load it up with games and such and let the kids play with it. Figure since it cannot make or receive calls anymore (or text messages either) it will make for a fun little toy.
Click to expand...
Click to collapse
Thanks! Yeah, in the past I have been a lot on Ubuntu and stuff like this is not forgiving for wine.
It's a darn shame that we can't just send these phones to Moto with $25 and get it fixed. Oh well!
KrisM22 said:
Thanks. That got me thinking - I wonder if you took the one with no IMEI and plugged it to Moto's Smart Assistant, would it recognize it? Would it allow you to force flash it?
Click to expand...
Click to collapse
Moto smart assistant can`t recognize the phone in rescue mode..
St.Noigel said:
Moto smart assistant can`t recognize the phone in rescue mode..
Click to expand...
Click to collapse
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
KrisM22 said:
I know it can't on yours, and most folks with this prob. I was wondering about MotoX4's case. But thanks for trying it!
I had high hopes for that smart assistant when I discovered it, but no joy. When we lost RSDlite, we lost a lot - unless they upgrade it...
Click to expand...
Click to collapse
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
MotoX4 said:
RSDlite? Lost? Is this what you seek? https://rsdlitetool.com/
Click to expand...
Click to collapse
6.2.4 won't recognize a Moto X4 after it is upgraded to Pie.
I used RSDLite since the times of the P2K and MAGX (Linux)... but since it's easier to use fastboot commands...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
joel_sinbad said:
...snip...
I have a stock X4 Android One around, if I want to flash Pixel Experience, can I go back to stock in the future?
Click to expand...
Click to collapse
In all probability, NO.
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
joel_sinbad said:
Then I'm gonna stay on Stock Rom, so... If I want to flash custom Roms, there's not way back...
Click to expand...
Click to collapse
If you read a lot on this forum, that's the message I see.
I agree, NO going back. You can, I have... flash any factory Pie rom . All will flash fine and no IMEI, wifi. Radios are gone. I use Google Fi and cell data services go wierd on custom roms, if you want carrier switching.
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
joel_sinbad said:
This makes me think that the Moto X4 is more dangerous than the back then Atrix 4G with their Tegra 2 chipset...
Click to expand...
Click to collapse
I don't recall thinking that the Moto Atrix 4g was at all dangerous when I had one - a rather nice phone imho, though that was a very long time ago. I don't think of the Moto X4 as "dangerous" - it is simply that there is not a correct understanding of the Pie file structure by the custom ROM devs such that their ROMs would not so change the file structure of the phone as to prevent it from being flashed back to stock.
Users need to recognize that, with this phone, you can't get back to stock if you flash any custom ROM.
afaik.
This change happened with the file structure and boot structure changes of the Pie update. Prior to that, folks could get away with all manner of mods. Devs for this phone need to approach modifications with the idea of assuring that any mod can be flashed back to stock, BEFORE it is released. That has not happened. And likely won't. User beware!
KrisM22..... Thank you for stating what I could not do as well.
kkjb said:
KrisM22..... Thank you for stating what I could not do as well.
Click to expand...
Click to collapse
we ALL do it, and CAN do it - all in hopes of saving some newbie from disaster!