Develop Bugs

[Q] Noob needing help

Hello peeps,
I've just come from an iphone so please forgive my stupidity. I've been looking around XDA and various other places for 2 days trying to sort my One X, but don't seem to be making any progress.
I currently only have access to the bootloader
I managed to unlock and root the phone, but then got stuck on a boot loop which I haven't been able to get out of. I was able to get into the OS, but had no cell or wifi, but now I'm just stuck in the bootloader after a failed flash of probably an incorrect RUU. The phone has been relocked.
I ran Vtool from post 7 here http://forum.xda-developers.com/showthread.php?t=1989358, and my main version is 2.17.206.2
I'm in the UK on the o2 network.
Can someone please help??

slixter said:
Hello peeps,
I've just come from an iphone so please forgive my stupidity. I've been looking around XDA and various other places for 2 days trying to sort my One X, but don't seem to be making any progress.
I currently only have access to the bootloader
I managed to unlock and root the phone, but then got stuck on a boot loop which I haven't been able to get out of. I was able to get into the OS, but had no cell or wifi, but now I'm just stuck in the bootloader after a failed flash of probably an incorrect RUU. The phone has been relocked.
I ran Vtool from post 7 here http://forum.xda-developers.com/showthread.php?t=1989358, and my main version is 2.17.206.2
I'm in the UK on the o2 network.
Can someone please help??
Click to expand...
Click to collapse
ok but what do you want to do now? keep it unlocked or not?

matt95 said:
ok but what do you want to do now? keep it unlocked or not?
Click to expand...
Click to collapse
I'd like to unlock it with a custom rom, but I'm quite happy just to have a working phone again.
Additional info, I also have access to CWM

slixter said:
I'd like to unlock it with a custom rom, but I'm quite happy just to have a working phone again.
Additional info, I also have access to CWM
Click to expand...
Click to collapse
Phone is also unlocked again using Hasoons all in one kit.

Happy to hear of a fellow iphone convert :thumbup:
Is there something in particular you did that caused the boot loop?
Do you by chance have a nandroid backup?

jonnyboiii said:
Is there something in particular you did that caused the boot loop?
Click to expand...
Click to collapse
I've got no idea to be honest.
I've got no back ups.

If you have access to cwm then you're not totally out of luck, I think your best option would be to flash a stock rom for your particular phone.

jonnyboiii said:
If you have access to cwm then you're not totally out of luck, I think your best option would be to flash a stock rom for your particular phone.
Click to expand...
Click to collapse
Can you direct me to a stock rom?

did you flash the boot.img when you got bootloops?

matt95 said:
did you flash the boot.img when you got bootloops?
Click to expand...
Click to collapse
Pretty sure i didn't

slixter said:
Pretty sure i didn't
Click to expand...
Click to collapse
that's why you got bootloops... when you flash a rom you need to flash its boot.img too

matt95 said:
that's why you got bootloops... when you flash a rom you need to flash its boot.img too
Click to expand...
Click to collapse
So do i need to flash the boot.img and the rom from CWM and I should be ok?

Just look around in the One-X forum, do some searching, see if you can find a stock rom to download to your computer then move to your phone.
CWM has this handy feature I think in the "mount" tab, where you can mount your phone as a usb device, from which your computer will pick it up and you'll be able to move the roms file to your phone for flashing.

jonnyboiii said:
Just look around in the One-X forum, do some searching, see if you can find a stock rom to download to your computer then move to your phone.
CWM has this handy feature I think in the "mount" tab, where you can mount your phone as a usb device, from which your computer will pick it up and you'll be able to move the roms file to your phone for flashing.
Click to expand...
Click to collapse
Thanks for the info - think I have a rom I can use.
1 more question before i continue, how do i flash the boot.img file? I have a zip with the rom / boot.img
I have mounted as usb storage and copied the zip file across

I've installed CM, after wiping cache, dalvik, system etc, but seem to be stuck on the JB animation screen.
Wondering if this means the OS is installing, or if I'm still stuffed....
I don't know if I need to do something with the boot.img file as the onlyl thing i did was load the zip file for CM

slixter said:
I've installed CM, after wiping cache, dalvik, system etc, but seem to be stuck on the JB animation screen.
Wondering if this means the OS is installing, or if I'm still stuffed....
I don't know if I need to do something with the boot.img file as the onlyl thing i did was load the zip file for CM
Click to expand...
Click to collapse
Personally I've flashed a total of three roms which isn't many, but in all my time spent reading threads of the latest and greatest roms I've never heard anything about a separate boot.img that you needed to flash... (perhaps a One-X specific thing?).
Just be patient with it when it's booting, the first boot after an install always takes longer.

jonnyboiii said:
Personally I've flashed a total of three roms which isn't many, but in all my time spent reading threads of the latest and greatest roms I've never heard anything about a separate boot.img that you needed to flash... (perhaps a One-X specific thing?).
Just be patient with it when it's booting, the first boot after an install always takes longer.
Click to expand...
Click to collapse
I do need to flash the boot.img first.
I'll do that once my battery gets some more charge.

How much charge does it have right now? It's important to always go into using CWM on a substantial amount of battery life. Upwards of %50 is recommended, but but you should do just fine with around 30, that is assuming you're able to tell.

slixter said:
I do need to flash the boot.img first.
I'll do that once my battery gets some more charge.
Click to expand...
Click to collapse
download the rom's boot.img and type with the phone in fastboot mode:
Code:
fastboot flash boot path/to/boot.img
after that your phone will boot up correctly

jonnyboiii said:
How much charge does it have right now? It's important to always go into using CWM on a substantial amount of battery life. Upwards of %50 is recommended, but but you should do just fine with around 30, that is assuming you're able to tell.
Click to expand...
Click to collapse
How do you tell how much charge it has?
matt95 said:
download the rom's boot.img and type with the phone in fastboot mode:
Code:
fastboot flash boot path/to/boot.img
after that your phone will boot up correctly
Click to expand...
Click to collapse
Fastboot won't let me flash cos of the low battery, so will let the phone charge for a bit then try again. Thanks.

[Q] What to do now?

So I have to admit I am pretty overwhelmed but the amount of information. So I wanted to find out from the community what do I do now.
My RAZR my is rooted, boot loader unlocked and on stock KK 4.4.2. I have no idea how to get the customer recovery on my phone the forrest ways as I have seen it many different ways. SO how it it I get TWRP on my device now. Once I do, is that how I install a rom? Will that wipe the stock one?

Easiest way to flash TWRP is through an app called "Flashify," which is found on the Google Play store. Download the correct version (TWRP 2.7.1.0 works well on the KK build) in ZIP format. Save to your phone. Open Flashify, backup your current recovery, and choose the new TWRP to flash. Reboot and see the new recovery.
In the new recovery, perform a full backup, throw it on your computer for safe keeping. There are a select few ROMs that work on the 3.4 kernel that the KK build uses, so if you would like to be opened to all the other ROMs, find the 98.30.1 update and flash it using your favorite method. After you flash back to the update, reinstall TWRP if it is gone, and then have fun.
To flash a ROM, just throw the ZIP file on your phone for your ROM, boot into TWRP and choose to install, and select the file(s) to flash. This does wipe the stock one. Perform a nandroid backup to save it.

xKroniK13x said:
Easiest way to flash TWRP is through an app called "Flashify," which is found on the Google Play store. Download the correct version (TWRP 2.7.1.0 works well on the KK build) in ZIP format. Save to your phone. Open Flashify, backup your current recovery, and choose the new TWRP to flash. Reboot and see the new recovery.
In the new recovery, perform a full backup, throw it on your computer for safe keeping. There are a select few ROMs that work on the 3.4 kernel that the KK build uses, so if you would like to be opened to all the other ROMs, find the 98.30.1 update and flash it using your favorite method. After you flash back to the update, reinstall TWRP if it is gone, and then have fun.
To flash a ROM, just throw the ZIP file on your phone for your ROM, boot into TWRP and choose to install, and select the file(s) to flash. This does wipe the stock one. Perform a nandroid backup to save it.
Click to expand...
Click to collapse
Thanks for this, it makes things much clearer. I noticed in the flashify app that you can flash bot rims. DO I have to do that too? or is it just the recovery that I need to worry about?

nxion said:
Thanks for this, it makes things much clearer. I noticed in the flashify app that you can flash bot rims. DO I have to do that too? or is it just the recovery that I need to worry about?
Click to expand...
Click to collapse
I'm not sure what you're saying, but recovery is the important thing. Just flash ROMs through recovery. Read directions for each ROM before you do so as well. Most require wiping the System partition at the least, but it's best to do a factory reset (via TWRP) before an install. Backup your data with Titanium.

xKroniK13x said:
I'm not sure what you're saying, but recovery is the important thing. Just flash ROMs through recovery. Read directions for each ROM before you do so as well. Most require wiping the System partition at the least, but it's best to do a factory reset (via TWRP) before an install. Backup your data with Titanium.
Click to expand...
Click to collapse
Sorry, I was trying to say in Flasify, there is the option to flash a boot and recovery image. I was asking if I had to do both.

nxion said:
Sorry, I was trying to say in Flasify, there is the option to flash a boot and recovery image. I was asking if I had to do both.
Click to expand...
Click to collapse
Boot image, I believe, is just the logo your phone displays when you first turn it on (think: red M, or after you unlock, the bootloader warning). Just the recovery is the important part.

xKroniK13x said:
Boot image, I believe, is just the logo your phone displays when you first turn it on (think: red M, or after you unlock, the bootloader warning). Just the recovery is the important part.
Click to expand...
Click to collapse
Boot image is linux kernel, do not try to touch it.

Klen2 said:
Boot image is linux kernel, do not try to touch it.
Click to expand...
Click to collapse
Good to know lol. Thank you.

[Q] Soft brick now I can only flash nightly?

I soft bricked my M8 and wiped the phone with twrp then tried to sideload the GPE rom I was using again and it wouldn't work. In fact I can't flash any rom that isn't cyanogen mod nightly for the m8... Also my bootloader changed from the white screen with the droid bots on a skateboard to a black screen with a single droid on it. Any idea why I can't flash anything besides cyanogen?

Rye Cribby Tree said:
I soft bricked my M8 and wiped the phone with twrp then tried to sideload the GPE rom I was using again and it wouldn't work. In fact I can't flash any rom that isn't cyanogen mod nightly for the m8... Also my bootloader changed from the white screen with the droid bots on a skateboard to a black screen with a single droid on it. Any idea why I can't flash anything besides cyanogen?
Click to expand...
Click to collapse
Did you try pushing the rom instead of sideloading it? Apparently sideloading in TWRP doesn't work, or doesn't work like it should
Try pushing it to the correct path and flash again.
Are you S-OFF?

BerndM14 said:
Did you try pushing the rom instead of sideloading it? Apparently sideloading in TWRP doesn't work, or doesn't work like it should
Try pushing it to the correct path and flash again.
Are you S-OFF?
Click to expand...
Click to collapse
Yeah, once I got the phone fixed I tried to load it normally. However it still didn't work. I tried other recoveries like Philz Touch too. Unfortunately firewater doesn't work for me.

Rye Cribby Tree said:
Yeah, once I got the phone fixed I tried to load it normally. However it still didn't work. I tried other recoveries like Philz Touch too. Unfortunately firewater doesn't work for me.
Click to expand...
Click to collapse
Try flashing the boot.img file that comes with the ROM first, then re-flash the ROM of your choice.
Code:
fastboot flash boot boot.img
fastboot reboot-bootloader
Go back into recovery of choice, wipe cache, dalvik-cache etc Then go to installed zip and select the ROM of your choice and flash the ROM.
Firewater won't work anymore for "later released" models that gets shipped with latest firmware. HTC patched it, you "MIGHT" be lucky if you still have an older device.
The developers of Firewater did however create another method to S-OFF the device. [Android][HTC S-OFF] SunShine for modern HTC devices
Sunshine is $25 but it works. It first checks your phone for compatibility before you pay for anything. That way if your device "isn't" compatible then it won't make you pay $25 for something that "won't" work.
Something to look into if you have $25 to spare :good:

BerndM14 said:
Try flashing the boot.img file that comes with the ROM first, then re-flash the ROM of your choice.
Code:
fastboot flash boot boot.img
fastboot reboot-bootloader
Go back into recovery of choice, wipe cache, dalvik-cache etc Then go to installed zip and select the ROM of your choice and flash the ROM.
Firewater won't work anymore for "later released" models that gets shipped with latest firmware. HTC patched it, you "MIGHT" be lucky if you still have an older device.
The developers of Firewater did however create another method to S-OFF the device. [Android][HTC S-OFF] SunShine for modern HTC devices
Sunshine is $25 but it works. It first checks your phone for compatibility before you pay for anything. That way if your device "isn't" compatible then it won't make you pay $25 for something that "won't" work.
Something to look into if you have $25 to spare :good:
Click to expand...
Click to collapse
I tried flashing the boot.img and it didn't work sadly. It fails as soon as I swipe to flash.

Rye Cribby Tree said:
I tried flashing the boot.img and it didn't work sadly. It fails as soon as I swipe to flash.
Click to expand...
Click to collapse
Did you flash in fastboot?Try to download twrp from its officical site.Also maybe you have downloaded a bad version of the rom.

Jyotirdeb said:
Did you flash in fastboot?Try to download twrp from its officical site.Also maybe you have downloaded a bad version of the rom.
Click to expand...
Click to collapse
There is no offical twrp for the AT&T version of the m8 and I did flash in fastboot. The ROM I used worked in a previous installation as well. It soft bricked after updating so I completely wiped the phone now it wont install.

I had a similar problem, I had to use the format option in twrp and then used RUU

gonzo237 said:
I had a similar problem, I had to use the format option in twrp and then used RUU
Click to expand...
Click to collapse
Do you have a link? Or something I could look up and find on my own?

Rye Cribby Tree said:
Do you have a link? Or something I could look up and find on my own?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2727831
Now this one is for the Verizon HTC, but maybe this will help you.

gonzo237 said:
http://forum.xda-developers.com/showthread.php?t=2727831
Now this one is for the Verizon HTC, but maybe this will help you.
Click to expand...
Click to collapse
Ah, I can't s-off, thank you for the reply though I'm sure someone else with this problem will find this helpful.

Rye Cribby Tree said:
Ah, I can't s-off, thank you for the reply though I'm sure someone else with this problem will find this helpful.
Click to expand...
Click to collapse
I'd still give the format option a try, I wasn't able to flash any roms except for the CM nightly as well, then I made it worse by trying to wipe the internal data which led to not being able to mount the internal partition, and couldn't even get into the bootloader until my phone battery died. I remember reading that the format would allow me to mount the internal storage. You may be able to fix the issues with a format and then try flashing a rom.

Did you try converting your phone over to GPE? That's what it sounds like you tried to do. If so then that is why nothing is working because the partitions are layed out differently from a stock sense M8. You need to wipe everything and run whatever RUU is available for your device and pray to god it works because you are s-on... You seriously should have been s-off before doing all of this. Being s-on is really going to complicate things for you bro... That's also probably why you can't fastboot the kernel. Find a RUU for your phone and run it. Post back here if you get any "main version" errors cuz then some tricks will need to be done.. Feel free to PM me, maybe I can assist directly getting you back up and running...

gonzo237 said:
I'd still give the format option a try, I wasn't able to flash any roms except for the CM nightly as well, then I made it worse by trying to wipe the internal data which led to not being able to mount the internal partition, and couldn't even get into the bootloader until my phone battery died. I remember reading that the format would allow me to mount the internal storage. You may be able to fix the issues with a format and then try flashing a rom.
Click to expand...
Click to collapse
Great news, your suggestion worked! I'm able to flash the sinless GPE 4.4.4 rom! No more nightly's for this guy.:good:

Internal SD Card Won't Mount

Phone won't boot

Basketballhero75 said:
Yesterday I tried to root, unlock bootloader, and S-Off my device:
1.) Started with root. I downloaded weaksauce (I was on a firmware that still supported it)
Obtained temporary root while booted into OS
2.) Firewater to gain S-OFF and unlock bootloader
Worked like a charm
3.) Flashed TWRP Recovery
Worked like a charm
4.) Downloaded and flashed a new ROM (Andybones)
Horrible idea.
After backing up my nandroid backup, I did a system wipe like always and tried to load the new ROM... didn't work. I got nervous and tried to restore backup. Didn't work.
I tried to RUU the phone back to stock. Didn't work. Phone went wonky somehow along the process and now my partition tables are all screwed up. Phone will not boot, only load HTC splashscreen.
I have maintained fastboot from the bootloader, and my custom recoveries still boot, but they cannot mount the internal SD card at all. I get the errors "E: Can't mount /Internal Storage" or E: Can't mount /cache".
I've flashed multiple RUUs and none of them seem to fix my issue. Even though the system installs, the phone can't boot from that system and any recovery I have can't help me either since it can't read into the SD card at all, or even detect it. My Internal storage space is defined as 0MB.
I'm stuck with a brick as of right now and could really use some help. If anyone has a skype or anything please reach out to me. I am left phoneless for the time being. This should be fixable since I have s-off still; I just don't have the experience to do it.
Click to expand...
Click to collapse
Exactly what file did you use to flash TWRP?

jpradley said:
Exactly what file did you use to flash TWRP?
Click to expand...
Click to collapse
What?

Basketballhero75 said:
I've used various different recoveries of TWRP including 2.7.1.2, and some others (not on my other computer at the moment). I also tried the most up to date CWM recovery. None of them are able to mount, repair, sideload, or fix any of the partitions.
Click to expand...
Click to collapse
I didn't ask you for the version of TWRP, I asked for the exact name of the TWRP image file you used. And where did you get it?

No idea

Basketballhero75 said:
A developer friend of mine was helping me out and he was doing all the downloading and flashing. I'm not too sure of the where but the file name is "TWRP_2.7.1.2.zip". and the CWM recovery was called "Recovery 6.0.4.8".
I'm 99.5% sure that it's not the recovery that's the issue here though.
Click to expand...
Click to collapse
The reason he is asking is because our model has different mount points than the other variants. Use the recovery in the below linked thread. It is flashable in ruu mode. He may have flashed an m7 recovery and not an m7wlv/m7vzw recovery.
http://forum.xda-developers.com/showthread.php?t=2867643
Sent from my HTC6500LVWBLU using XDA Free mobile app

Have your friend who helped you inform you if he used a specific Verizon ruu and recovery, as using an International, AT&T, Sprint, GPE, etc ruu will wreak havoc and cause headaches.
Use the ruu and follow dottdat's instructions in the above thread. If you can boot to bootloader, then all is not lost, just follow the instructions and commands to ruu with the Verizon specific ruu and recovery found in that thread and you should be set.
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
Have your friend who helped you inform you if he used a specific Verizon ruu and recovery, as using an International, AT&T, Sprint, GPE, etc ruu will wreak havoc and cause headaches.
Use the ruu and follow dottdat's instructions in the above thread. If you can boot to bootloader, then all is not lost, just follow the instructions and commands to ruu with the Verizon specific ruu and recovery found in that thread and you should be set.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
His friend didn't use the wrong recovery ?
Sadly this one appear to be a case of bad emmc

@Basketballhero75, Have you found resolution to your issue?

TonyStark said:
@Basketballhero75, Have you found resolution to your issue?
Click to expand...
Click to collapse
Yes. He did. New phone.
If you have one in this state I can share a couple ideas.

How do I backup my stock recovery?

I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?

tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist

v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile

Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---

Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.

tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)

Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.

redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.

Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.