Related
hi guys
i've unlocked my HTC ONE X + international!
but now i can't go further the HTC logo
i tried fastboot, flashing boot and recovering recover.img. but nothing go right.
Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium
o_O said:
Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
after i unlocked the phone i've used fastboot to fastboot recovery.img
and that's all i did .
now i have low battery
Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium
o_O said:
Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???
tyomaus said:
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???
Click to expand...
Click to collapse
If you've gotten the recovery installed, then you can sideload the rom onto the phone. I can give you instructions to do that with TWRP as your recovery. With your phone connected to your computer, enter the recovery from the bootloader. Choose the "Advanced" button, and then "ADB Sideload" and then swipe to start the sideload process.from your command line on your computer, you can now start the sideload process:
Code:
$ adb sideload name-of-rom-zip-file.zip
Obviously you would need to put the actual name of your rom's zip file and make sure your zip is in the correct directory to be picked up by the command. You should see the rom begin to upload to your phone, and when it's done, it will automatically flash.
I've found that sometimes sideload can take a little while to detect the phone but usually it detects it immediately. If it's taking a while, try running the following command and then do the sideload again; it might help:
Code:
$ adb kill-server
$ adb sideload name-of-rom-zip-file.zip
Don't forget that because we haven't gotten S-OFF for our device yet, we need to flash the kernel separately. Just open the rom zip file, and extract "boot.img". Then you need to enter the bootloader and flash that to your phone with this command:
Code:
$ fastboot flash boot boot.img
Hopefully that helps to sort your phone out.
thanks for help! )))
, MAN u r the best!!!! thanks a lot ! ))))
No problem! Glad to help.
o_O said:
No problem! Glad to help.
Click to expand...
Click to collapse
hi, i have one more problem (((
i've installed custom ROM, but only AOKP is working but not properly, after installing says there is no SD card ((
others stuck in loading screen.
This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.
o_O said:
This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.
Click to expand...
Click to collapse
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!
tyomaus said:
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!
Click to expand...
Click to collapse
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?
Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.
cool
reaper90 said:
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?
Click to expand...
Click to collapse
thank you MAN!!! it's working! :good:
yourthebest
o_O said:
Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.
Click to expand...
Click to collapse
nothing to say, just HUGE THANKS!!! )))
i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !
Sure, it's possible, and you have a couple of options depending on how "stock" you want to go.
If you just want to go back to a Sense rom, you can go to the One X+ Android Development forum and download any of the international roms from there. You would need to flash Elite kernel or hXORe kernel, which can also be found in that forum, and the process for flashing the rom and kernel is exactly the same as the AOKP/CM roms you already tried.
If you specifically need to get back to STOCK, then it's a little more complicated. You need to run a RUU (Rom Update Utility) for your device, which will put the original software back on your phone, but you need to remember to re-lock your bootloader before you run it, or it will fail. You can download the correct RUU for your device here (http://androidfiles.org/ruu/?developer=ENRC2B).
I would hazard a guess that you can find the right version by matching the radio version on your phone to the radio version on the RUU, along with your geographic location. You can find your phone's radio version by going to settings > about phone > baseband version. A quick explanation behind that logic is that a normal rom-flash won't touch your phone's radio, so you're likely to still have the same radio version that your phone shipped with.
WARNING, however, messing with your radio can brick your device so please please make sure you have the right one before you flash. I'm not sure which is the correct one for your device and the only RUUs I've ever flashed were way back in the early Windows Mobile days, so hopefully someone else here can give you better direction on that point.
Finally, if I were to give my opinion, you're better off taking a rom from the Android Development forum. I'm a die-hard AOSP fan, but I've flashed and played with the roms in there and our Sense devs have done a great job with the X+. The only reason I'd go back to stock is if I had to for warranty purposes.
tyomaus said:
i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !
Click to expand...
Click to collapse
As already said, I'd recommend installing a stock like custom rom, for example Android Revolution HD, it's very close to stock. You can find stock kernel/boot.img in the thread and if you want it as close to stock as possible you can just leave out all the tweaks options in aroma installer.
reaper90 & thank u BROS! )))
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
DooMLoRD said:
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system [UPLOADING]
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
scrubber said:
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
Click to expand...
Click to collapse
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
DooMLoRD said:
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
Click to expand...
Click to collapse
Ok. Will arrange topic
scrubber said:
Ok. Will arrange topic
Click to expand...
Click to collapse
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
No problem, any source and can parts
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
We can wait
joluke said:
We can wait
Click to expand...
Click to collapse
scrubber said:
No problem, any source and can parts
Click to expand...
Click to collapse
done
https://mega.co.nz/#!4RNx0Jaa!trTgJIXt8bB9R8LW6z3IVejSRV0MfqNvviD769UUsDo
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
pudgewack said:
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
Click to expand...
Click to collapse
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
ekrunch said:
Forgive the long post
Click to expand...
Click to collapse
Nice, well explained post.
ekrunch said:
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Click to expand...
Click to collapse
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
ddslee said:
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Click to expand...
Click to collapse
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
ekrunch said:
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
Click to expand...
Click to collapse
thanks for creating it i was lazy to write all this
DooMLoRD said:
....
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
...
Click to expand...
Click to collapse
Preview comes out ok as the hardware does initialize. The issue is, from what I have seen and other who may have corroborated this, is the AF on the camera. You see, photosphere actually works well, just not the regular camera. Someone else mentioned that apps using infinity focus work as well.
My guess is that something in 4.4.3 and 4.4.4 (maybe in the kernel?) is looking for the missing DRM keys from devices with unlocked BL. Several people have already stated that they have no issues with their cameras, with the only difference being the locked bootloader in their devices. Considering that Sony had done something similar with the Z1 last year, I would not be surprised if it was the case here as well. Not sure why this would be the case for a GPE unit as it has no proprietary software (other than X-Reality)...
As I said, nothing but a guess albeit it does make sense (to me anyways).
Finally!!
Finally got my GPE to update using ekrunches excellent post..it took a little fiddling, (WIPE!! REALLY!!) but everything else went quite smoothly. I did find that fastboot -w didn't format partitions on cache and data and ended up in stock recovery to do a full wipe, after which things worked perfectly. Before that it was bootlooping on me. Didn't fix the camera though. I may leave this sucker mostly stock until someone fixes the camera...and on that note-I unlocked my bootloader immediately on getting the phone, before any updates ran. I've been considering the idea that if you unlocked before 4.4.2, that might be what's messing the camera up. I don't have any evidence for this though, it's just a guess.
DooMLoRD said:
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
Click to expand...
Click to collapse
hahahaha I did. But it's the same for the boot and FOTAKernel images. What kept throwing me was one working while the other didn't but they were both the same type of file. How nice of Sony to do this... *cough cough*
DooMLoRD said:
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Click to expand...
Click to collapse
So is there a better way to flash that boot image or is this it?
DooMLoRD said:
thanks for creating it i was lazy to write all this
Click to expand...
Click to collapse
You're quite welcome. Thank you for all of the dumps, kernels, write ups, etc. It is much appreciated. I've been leeching information from this forum for years with no contribution other than some donations so I'm glad to help out. I was beating my head up against the wall when I wrote that first post as it was driving me crazy that I couldn't flash that boot image. I've been spoiled by Nexus devices.
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Pallavgarg10 said:
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Click to expand...
Click to collapse
Depends what you are trying to achieve?
Fully update your new GPe ZU?
From 4.4.2 to 4.4.4?
Already rooted or not, if not I would just flash the OTAs
I just want to update to 4.4.4 with as little modification as possible
Latest OTA for intl WWE OTA_T6_UL_K44_SENSE60_MR_hTC_Asia_WWE_3.23.707.1-3.14.707.3_release_385121
145.58MB - Contains important enhancements and bug fixes, including : System security improvement [Download]
International hboot 3.23.707.1 no red text modified
You must be S-Off to do this! This one's for International variant only
I can not be held responsible for this zip please flash at your own risk!
Download from attachment
Place the zip in your adb/ fastboot directory on your computer
Put the device in fastboot mode and connect to the computer
Enter the following commands from cmd from the adb/ fastboot directory:
Code:
[COLOR="Red"]fastboot oem rebootRUU
fastboot flash zip 3.23.707.1nored_hboot.zip[/COLOR]
Note: The progress on the screen may not fully 100% but it's normal. but make sure it's writen "successfully" on the cmd windows on your PC
Code:
[COLOR="Red"]fastboot reboot-bootloader
fastboot reboot[/COLOR]
@mafyas
Any chance you could get me a system dump of that or twrp backup
Desperately Require
Could you please share Nand Backup or TWRP backup, also the stock recovery.
I have bricked my max. I was earlier on 3.15.707.101
Flyhalf205 said:
@mafyas
Any chance you could get me a system dump of that or twrp backup
Click to expand...
Click to collapse
My pleasure @Flyhalf205 , system dump in progress. I will share by torrent cause i got no proper file hosting.
edit :
Wallaooo... 2.36GB system dump.. too big for upload..
mafyas said:
My pleasure @Flyhalf205 , system dump in progress. I will share by torrent cause i got no proper file hosting.
edit :
Wallaooo... 2.36GB system dump.. too big for upload..
Click to expand...
Click to collapse
TWRP backups are normally 1.2GB
Flyhalf205 said:
TWRP backups are normally 1.2GB
Click to expand...
Click to collapse
TWRP 2.7.0.0, system boot backup. 1.09GB
tkhads said:
Could you please share Nand Backup or TWRP backup, also the stock recovery.
I have bricked my max. I was earlier on 3.15.707.101
Click to expand...
Click to collapse
Sorry mate, i dont have 3.15.707.101
That's my best max speed quota for torrent @Flyhalf205, transfer rate at average of 570kB/s .. reserve some for 9gag tv. lol
OP updated with modified no red text intl hboot 3.23.707.1
Thanks. Was hoping to base NuSense off of this but can't get anything to bot. Thanks for uploading.
Flyhalf205 said:
Thanks. Was hoping to base NuSense off of this but can't get anything to bot. Thanks for uploading.
Click to expand...
Click to collapse
No need to thank me my man.. You did great works for Max family. Feel sorry, my sys twrp backup didnt work for NuSense. Any chance you give a try my system dump 2.37GB? If yes, I will make torrent again. Maybe something goes wrong with previous twrp backup.
Need Version details
mafyas said:
Sorry mate, i dont have 3.15.707.101
Click to expand...
Click to collapse
No worries, Is it possible to share your version details (fastboot getvar all) excluding your IMEI and other personal details. Want to ensure the MID and CID match before flashing the zip. Thanls!!!
could you please seed twrp torrent...
Got my 3.23.401.1 update today in the UK.
help
mafyas said:
Latest OTA for intl WWE OTA_T6_UL_K44_SENSE60_MR_hTC_Asia_WWE_3.23.707.1-3.14.707.3_release_385121
145.58MB - Contains important enhancements and bug fixes, including : System security improvement [Download]
International hboot 3.23.707.1 no red text modified
You must be S-Off to do this! This one's for International variant only
I can not be held responsible for this zip please flash at your own risk!
Download from attachment
Place the zip in your adb/ fastboot directory on your computer
Put the device in fastboot mode and connect to the computer
Enter the following commands from cmd from the adb/ fastboot directory:
Code:
[COLOR="Red"]fastboot oem rebootRUU
fastboot flash zip 3.23.707.1nored_hboot.zip[/COLOR]
Note: The progress on the screen may not fully 100% but it's normal. but make sure it's writen "successfully" on the cmd windows on your PC
Code:
[COLOR="Red"]fastboot reboot-bootloader
fastboot reboot[/COLOR]
Click to expand...
Click to collapse
sorry for asking. but i don't understand. do i need to flash 3.23.707.1nored_hboot.zip first? and then? what to do? do the same thing for the ota zip? flash via fastboot?
pekji said:
sorry for asking. but i don't understand. do i need to flash 3.23.707.1nored_hboot.zip first? and then? what to do? do the same thing for the ota zip? flash via fastboot?
Click to expand...
Click to collapse
Get the OTA installed via stock recovery and later flash modified hboot to removed red text development.
mafyas said:
Get the OTA installed via stock recovery and later flash modified hboot to removed red text development.
Click to expand...
Click to collapse
So what i do is flash stock recovery and then install OTA zip via fastboot? Or can i download and install OTA directly from my phone? Sorry. I'm a bit confused here.
Sent from my HTC One max using XDA Free mobile app
pekji said:
So what i do is flash stock recovery and then install OTA zip via fastboot? Or can i download and install OTA directly from my phone? Sorry. I'm a bit confused here.
Sent from my HTC One max using XDA Free mobile app
Click to expand...
Click to collapse
Cant flash via fastboot, flash in recovery using method install. Make sure you have pure stock sense6 rom. Otherwise, it will fail to install OTA, no brick no worries, just fail and need to repeat process.
Ok. I will try tonight. Thanks a lot.
Edit : failed. i'm a bit confused with the steps really. i flash stock recovery but when i reboot to recovery the triangle and ! picture comes out. what i should do really? it would be very nice of you if you can teach me from step 1. thanks. sorry for asking too much.
Sent from my HTC One max using XDA Free mobile app
Anyone have STOCK ROM for hTC_Asia_WWE ???
LAF NUKER wipes your Download mode and let you use Fastboot instead.:
Do this on your own responsibility, if you bricked your phone in some weird way then don't look at me.
But with this simple thing you can't brick your phone only if you flashed the wrong zip which wasn't from me.
This is more meant for developers/testers.
Click to expand...
Click to collapse
I was getting irritated that my Fastboot mode dissapeared everytime when I flashed some lollipop stock based rom as those all included bootloader files, so I had to first attempt to get into the rom itself or recovery to wipe it again over and over. So I thought by myself why won't I make something easy and flashable?
This lightweight flashable zip from 2-4KB is tested by me multiple times so after you flashed it I HIGHLYsuggest that you need to test or you can enter download mode and see if it shows now fastboot. If so then everything succeeded like it should, it has an succes rate of 100% as nothing could actually go wrong with this.
This script/method should also work for the G3 and some other LG devices which have this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/laf
For the one's who care the shell script is located in the update-binary, updater-script is just dummy.
If you want to revert back, just flash the jb/kk/lp bootloader files.
Download:
https://docs.google.com/uc?authuser=0&id=0B1u3mnq0nstfZVN1eVQ3bEw5ODQ&export=download
Mirror:
https://www.androidfilehost.com/?fid=23991606952610950
Credits:
Jackpotclavin for the method to get into fastboot mode
Chainfire for the shell updater-script method
osm0sis for the guide about the shell updater-script
Be careful maybe we can't use fastboot to flash it stuck.
somboons said:
Be careful maybe we can't use fastboot to flash it stuck.
Click to expand...
Click to collapse
I experienced once already when it was stuck, recovery kinda screwed up and modified stock rom didn't wanted to boot anymore and I just flashed a new recovery through fastboot mode and it worked properly. I am also still flashing test kernels through fastboot as I am used to that coming from the Nexus family.
This is also more meant for the real flashaholics and or developers as I experienced many times already on my G2 that download mode didn't worked after flashing several stock roms. So this is especially for the people who also face the same issue as me with download mode and who wants to have an backup if something would go wrong. Maybe I could also make later something like savoca made with autoboot but then on the download mode partition with option to boot into download mode or fastboot. But that would probably take some time to make it and I am not sure whats the size of the other available partitions.
Fastboot supports kdz files? As I use Google Nexus, Fastboot supports img files. So how are we gonna flash kdz files when we use Fastboot?
But you can extract files from kdz. And flash them on fastboot.
yes @ceza1380 just like kimitza said you have to extract the images but I am not sure or you are able to flash all the images through fastboot. What you could do is flash with fastboot recovery and download a flashable stock rom or just the bootloader files and flash it through the recovery.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void... Well, probably not.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* A lot.
*
* Tl;dr: if your device crashes and burns, I'm sorry, but I'm not to be blamed.
*/
Hey guys.
This is a guide on how to install official Android 8.1.0 "Oreo" on our beloved, forgotten, poor Moto G5s (montana). As you all may know, Lenovorola still hasn't released Oreo for everyone worldwide. Only a few Latin American countries are receiving the update, with Brazil due to receive it Soon™, since we've already received the August security patch (still Nougat though :/).
Update 2018.09.29: Brazil and India have also started receiving Oreo, but with a different build (OPP28.65-37-2).
However, this is Lenovorola we're dealing with, so I went ahead, captured the OTA and created a TWRP flashable zip, by patching the June firmware (NPPS26.102-49-11) with said OTA. And also, there's the standard .xml.zip to be used with fastboot, directly from Moto.
For those of you who want to keep everything stock, locked bootloader and all, I recommend going with the fastboot zip. For those who already have unlocked their phone's bootloaders and have TWRP installed, or are coming from a custom ROM but don't want to fiddle around with fastboot, you should use the TWRP flashable zip.
I can't stress this enough. ALWAYS BACK UP YOUR STUFF!!!! Do a TWRP backup (data, system, boot). I recommend backing up the contents of your internal storage as well. And for those willing to downgrade at some point, back up your persist and efs partitions, otherwise you'll lose IMEI!
Oh, and I assume you already have adb, fastboot and the Motorola USB drivers installed. In case you don't...
Motorola USB Drivers
Android SDK Platform Tools (includes adb & fastboot)
If you use Linux, you don't need to install any drivers, but you may have to configure udev to allow fastboot to detect your device. But that, along with telling how to configure adb and fastboot, is beyond the scope of this thread.
I don't know how things work in the Apple side, so kindly don't ask me how to do that on macOS.
This firmware should work on all Moto G5s models (XT1791/2/3/4/5/7). I can't tell if it works on model XT1799-2 (aka Green Pomelo / Qingyou).
A few warnings:
1. Forced encryption has not been disabled. So, if your phone is not encrypted, it will be encrypted again upon the very first boot. Don't interrupt the process, otherwise you'll lose ALL of your data! (You can flash @Zackptg5's dm-verity / forced encryption disabler if you want to)
2. Xposed doesn't work, whether it's installed to /system or via Magisk (systemless). I've already opened an issue on GitHub and am awaiting a reply.
3. (Fastboot only) Updating to this firmware will also update your bootloader and partition table. If you're unsure about that and/or afraid of a possible hard brick, skip the gpt and bootloader lines.
4. Please install the proper build for your software channel. For retbr and retin, use OPP28.65-37-2. For the other channels, go with OPP28.65-37.
5. If your phone's software channel is retbr or retin and you have already flashed the -37 build, you can simply dirty flash the -37-2 build over it. No need to factory reset / fastboot erase userdata.
With that out of the way, let's get to what matters most.
Downloads:
Build OPP28.65-37 (retla):
Fastboot ZIP (Android File Host | MEGA)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Build OPP28.65-37-2 (retbr & retin):
Fastboot ZIP (Android File Host)
TWRP Flashable ZIP (Google Drive)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installation Guide:
Fastboot ZIP:
1. Download (obviously)
2. Extract the contents to a folder of your choice
3. Go to the folder which you extracted the files to
3. Inside the folder, open a command prompt, PowerShell, terminal or whatever you use as a command line interface
4. Put your device into fastboot mode if you haven't already done that (just hold Vol Down + Power for a while) and connect it to your PC
5. Execute the following commands:
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
reboot
6. Have fun
Click to expand...
Click to collapse
TWRP Flashable ZIP:
1. Download (duh)
2. Put the file at the root of your internal storage (/sdcard)
3. Reboot to TWRP
4. Do a factory reset (optional if coming from stock Nougat) and then format /system
(If your device is encrypted and you want to remove encryption, you will have to format /data and then flash the forceencrypt disabler I mentioned above after flashing the ROM)
5. Flash the zip
6. Reboot
7. Have fun
Click to expand...
Click to collapse
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
@Cesarcami53 for telling us that the update was out for retla
@erfanoabdi for his Motorola OTA Link Generator and IMG Patch Tools
@lohanbarth for mirroring the fastboot zips to AFH / Mega
In case I forgot someone, please do let me know.
F.A.Q. (Read this before crying!!!!)
Q: Why did you come up with this?
A: Because Lenovorola is pulling a Samsung, taking forever to officially deliver the Oreo update to everyone.
Q: ERMAHGERD DIS ROM SUCKZ, MAH BATTERY IS DEAD IN 30 MINS, PLZ HALP!
A: Please do blame Motorola, or yourself, or your apps' developers, but not me. I haven't got anything to do with that. I haven't changed anything.
Q: What works and what doesn't?
In theory, everything should work, and nothing should be broken, since this is a stock ROM.
Q: Will you add feature xyz?
A: No.
Q: Why no inbuilt root/Magisk/xyz/abc?
A: Because not. 1. There's something called freedom of choice, and that must be respected. / 2. I want to keep everything as bit-perfect as possible, and as close as possible to what you would get by flashing a real OTA.
Q: How do I report bugs?
A: If you wanna report a bug, send me a logcat. In case of a kernel panic, /proc/last_kmsg will help.
Q: How do I flash this?
A: I suggest you scroll up and read the OP. The instructions are there.
Q: How do I tweak this ROM?
A: For theming, there's full OMS/Substratum support. Xposed doesn't work, so no extra tweaks for now.
Q: This kid is such a n00b!
A: Oh well then, why don't you go do something like this yourself, instead of criticizing my work and wasting your time?
Reserved again
Oh look! Another reserved post!
And as a bonus, have this nice little dark boot logo from me, which hides that dreaded "N/A" and also "bad key" things. Extract the zip file and flash the logo3.bin file inside using fastboot:
Code:
fastboot flash logo logo3.bin
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Which security pet
Official or Soak test?
Kamin4ri said:
Thanks to:
@NZedPred for the excellent tutorial on how to build flashable zips based on stock firmware and/or OTAs
[/SIZE]
Click to expand...
Click to collapse
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
I can tell you that this build work very well in european distribution (reteu).
Basicly everything work including sim and nfc(paying not tested yet)
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Also not able to download, please offer another download Location!
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
ilovepanda said:
Good Night Guys, if I install it for twrp will the installation fiddle with the bootloader?
Click to expand...
Click to collapse
No. Your bootloader will be updated if, and only if, you install via fastboot and actually execute the respective command.
[email protected] said:
Official or Soak test?
Click to expand...
Click to collapse
This is the official firmware released for retla (Latin America). However, the soak tests in Brazil haven't finished yet. I'll update the OP with the link for the Brazilian firmware as soon as it's available.
NZedPred said:
Hey man, I am so thankful that someone has found my guide and made something for another device.
Well done, and best of luck with this thread. :good:
Click to expand...
Click to collapse
Thank you, friend! I'll be definitely using that guide again.
7opex0 said:
Do I need to unlock my bootloader on Russian type of XT1794 to flash this firmware via PC?
Click to expand...
Click to collapse
Only if you're flashing via TWRP. If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
giugiura said:
The link with the Fastboot ZIP doesn't work for me, I guess I'm the unlucky one. Is there any chance that you can upload it elsewhere? Thanks.
Click to expand...
Click to collapse
dau999 said:
Also not able to download, please offer another download Location!
Click to expand...
Click to collapse
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Kamin4ri said:
If you're using fastboot, there's no need to unlock your bootloader, since this is an official firmware signed by Motorola.
Click to expand...
Click to collapse
Okay then! Thanks for information.
7opex0 said:
Okay then! Thanks for information.
Click to expand...
Click to collapse
Not at all!
Kamin4ri said:
I have the zip here, but uploading it using my home Internet connection would take ages. I'll do it next Monday, I'll use my university's connection. I can get 100+ Mbps transfer rates, so it should be really quick for a file this size (1.5 GB).
Click to expand...
Click to collapse
Please upload it on some other cloud so that we can download it thanks for help sir
In advance