Related
is there any way to flash a zip with a locked bootloader? its not a rom zip but a zip whic contaings some mods like beats audio and stuff like that. it just takes tooo long to copy and set permissions manually. i was thinking rom manager but im not sure if you have to be unlocked or if it will even work. maybe theres another app or something. or maybe some one knows a way to do it using adb. i am rooted by the way.
You must be unlocked, rooted, and have a custom recovery (TWRP, CWM) installed to flash any zip of any nature. I use TWRP, it was easy enough to install, has a nice UI, and has less ware on the volume buttons. Happy rooting
AnnonymousFalcon said:
You must be unlocked, rooted, and have a custom recovery (TWRP, CWM) installed to flash any zip of any nature. I use TWRP, it was easy enough to install, has a nice UI, and has less ware on the volume buttons. Happy rooting
Click to expand...
Click to collapse
Untrue, you don't need to be rooted.
Unlocking is mandatory, the only way to install a custom recovery. Once unlocked you flash the recovery with fastboot, then you can flash ROMs.
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
fcortes626 said:
is there any way to flash a zip with a locked bootloader? its not a rom zip but a zip whic contaings some mods like beats audio and stuff like that. it just takes tooo long to copy and set permissions manually. i was thinking rom manager but im not sure if you have to be unlocked or if it will even work. maybe theres another app or something. or maybe some one knows a way to do it using adb. i am rooted by the way.
Click to expand...
Click to collapse
Whatever the content of the zip you need a recovery. ROM Manager don't do that at all. ADB sure, unzip the file on your computer, then 'adb remount' first to mount r/w sytem, and 'adb push <your file path> <destination path>'.
Striatum_bdr said:
Untrue, you don't need to be rooted.
Unlocking is mandatory, the only way to install a custom recovery. Once unlocked you flash the recovery with fastboot, then you can flash roms'.
Click to expand...
Click to collapse
Sorry, thats correct, I've just always rooted first.. I apologize :/
well i found an app that installs cwm on the system partition but it only works for the xperia and i emailed the developer and he said the belives he can make it work but wouldnt know where to start
fcortes626 said:
well i found an app that installs cwm on the system partition but it only works for the xperia and i emailed the developer and he said the belives he can make it work but wouldnt know where to start
Click to expand...
Click to collapse
???
Mind linking that?
I've never heard of a recovery installed on /system. The only way i know to install CWM without unlocking is by a bootstrap hijack (Moto devices).
My suggestion is to just unlock your tablet, perform the unbrickable mod, and flash at will.
Sent from my DROID RAZR using Tapatalk 2
joshw0000 said:
???
Mind linking that?
I've never heard of a recovery installed on /system. The only way i know to install CWM without unlocking is by a bootstrap hijack (Moto devices).
My suggestion is to just unlock your tablet, perform the unbrickable mod, and flash at will.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
here is the app https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
if i was to unlock i would probably need to send it to asus first because i am having the wifi drop issue. but i have read that some people cant unlock their prime after getting it back from asus
fcortes626 said:
here is the app https://play.google.com/store/apps/details?id=com.pvy.CWMinstaler&hl=en
if i was to unlock i would probably need to send it to asus first because i am having the wifi drop issue. but i have read that some people cant unlock their prime after getting it back from asus
Click to expand...
Click to collapse
That's pretty badass. Never had a Sony phone so I'd never heard of this.
Sent from my DROID RAZR using Tapatalk 2
joshw0000 said:
That's pretty badass. Never had a Sony phone so I'd never heard of this.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
yea and if it worked for our device it would be really big. i think you can install cwm on external sdcard too but dont know how that works either.
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
This system nandroid image has been created for developer use. So, it's not for everyone to play around with. It does not have the new bootloader or boot image, both of which are required to use this system image. It was created using my modified copy of the TWRP 2.2.2 recovery image.
The TWRP 2.2.2 recovery image below is a modified version of the original TWRP 2.2.2 recovery (credits TeamWin). I have merely replaced the kernel within the recovery image with the new JB kernel, thereby allowing it to work with the new bootloader. This is an un-blob'd recovery image. If you wish to directly flash this image, you need to have nvFlash enabled. Else you need to make a blob pack and flash it.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
USE AT YOUR OWN RISK!!! THE NEW TF201 JB BOOTLOADER IS ESSENTIAL REQUIREMENT!!! BE CAREFUL OR YOUR COULD BRICK YOUR DEVICE
Let the modding begin!!!
tf201-jro03c-system.ext4.win (The system nandroid image)
twrp-2.2.2-jb.img (The un-blob'd modified TWRP recovery)
tf201-jro03c-deodex.zip (De-odexed system apps and framework jars only)
tf201-jb-bootloader.blob (Blobpack of the new JB bootloader)
tf201-jb-kernel.blob (Blobpack of the new JB kernel)
tf201-jb-stock-recovery.blob (Blobpack of the new JB stock recovery)
tf201-jb-twrp-recovery.blob (Blobpack of the my modified TWRP recovery)
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Thanks for posting.
Are you going to post the boot image?
Turge said:
Thanks for posting. Can you fix the link to the boot image? It's just pointing to d-h.st.
Click to expand...
Click to collapse
If anyone else needs this its at the link here, Craig was working hard and missed it
http://d-h.st/JMk
Thanks for putting this together Craig, you've done alot for us as of late, loved your CM10 builds
thank you for pulling this together, i look forward to what comes from this
ravenholm said:
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Click to expand...
Click to collapse
Wookie modified it so it would work for the TF300 JB base so my guess would be no.
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
craigacgomez said:
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
...
Click to expand...
Click to collapse
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Moe5508 said:
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Click to expand...
Click to collapse
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
biggem001 said:
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
Click to expand...
Click to collapse
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Moe5508 said:
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Click to expand...
Click to collapse
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Ahhh, waiting a few more weeks/months wont hurt anyone ;p
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Yay, thanks for working on that! I am tempted to flash the jb stock image (from unpack) and do all the above, but still, I'd rather have a more reliable method step by step instruction set.
And yes, there is a new partition scheme. Flashing the image with old partition scheme intact will cause errors that could be fixed by nvflash.
Hawke84 said:
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
Any I'm going to state this again... unless you have the new TF201 JB bootloader, do not attempt to use the recovery or nandroid image...
jermaine151 said:
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
Click to expand...
Click to collapse
Thanks, no rush mate
Sent from my HTC Sensation Z710e using xda premium
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
ManOnTheMoon said:
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
Click to expand...
Click to collapse
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
craigacgomez said:
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
Click to expand...
Click to collapse
Let me know if u want me to test I have nvflash and some time this evening. I also half know what I'm doing
Sent from my HTC Sensation Z710e using xda premium
Dumb question but as I have only ever used CWM and 4ext, I am unsure what settings to use for backing up my rom in TWRP. Can someone enlighten me so that I can perform a backup just in case future flashing goes wrong I have a full backup to return to.
Would I be right in thinking there is no point in backing up the boot image, so I should just choose system and data? I just figured recovery can't flash a boot image anyway.
Bit confusing with the internal storage.
Thanks,
maritimesbob said:
Dumb question but as I have only ever used CWM and 4ext, I am unsure what settings to use for backing up my rom in TWRP. Can someone enlighten me so that I can perform a backup just in case future flashing goes wrong I have a full backup to return to.
Would I be right in thinking there is no point in backing up the boot image, so I should just choose system and data? I just figured recovery can't flash a boot image anyway.
Bit confusing with the internal storage.
Thanks,
Click to expand...
Click to collapse
You should use the TWRP
You boot into recovery mode.Select Backup.Tick all the options (system, data, cache etc..) And then drag the slider from left to right is done. Wait it finished backup and reset the machine you already have a full rom backup that
I wish you success
I am trying to run twrp without flashing it to the recovery partition. I read that I may be able to run it (once, without any permanent modification) with:
Code:
# fastboot boot openrecovery-twrp-2.3.3.0-enrc2b.img
downloading 'boot.img'...
OKAY [ 0.896s]
booting...
OKAY [ 0.008s]
finished. total time: 0.904s
but after typing that (htc one x+ intl unlocked) the device reboots and remains stuck at the boot with the HTC logo. My current goal would be to run twrp to backup the recovery partition (as first noob step) and possibly without making any permanent change to the phone. Is that even possible? Am I doing something wrong? Thank you.
AW: [Q] TWRP backup
it doesnt work.
recovery could not be backup at S-ON state
R: [Q] TWRP backup
it doesnt work.
recovery could not be backup at S-ON state
Click to expand...
Click to collapse
So I would be able to flash (write) it but not back it up (read) at S-ON?
If that's the case I would still prefer not to overwrite the recovery in order to use twrp to backup the system or for any other task. I also would like to test twrp before eventually flash it. It looks like:
Code:
fastboot boot boot.img
would be handy if I could get it to work.
Should I get to the S-OFF state for that?
Sent from my HTC One X+ using xda premium
fastboot flash boot boot.img
fastboot flash recovery <insert.img name here>
R: [Q] TWRP backup
Lloir said:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Sorry for my extreme cautiousness but I'm still researching before taking action.
Is flashing the boot.img potentially dangerous? If by accident I'll flash the wrong boot.img would I brick my device? For "brick" I mean a state where I can fix the issue only by physically opening the phone (I'm not concerned about data loss).
If the boot.img is wrong/damaged would fastboot still work?
Lloir said:
fastboot flash recovery <insert.img name here>
Click to expand...
Click to collapse
I have no doubt that this is going to work but I was wondering if I could run it without any modification as the "fastboot boot" command suggests.
Anyway at the moment what I want to do is a full backup of my device (boot.img, recovery.img, ...) so that later on I can eventually revert everything. Is there any guide about this?
Sent from my HTC One X+ using xda premium
maritimesbob said:
Dumb question but as I have only ever used CWM and 4ext, I am unsure what settings to use for backing up my rom in TWRP. Can someone enlighten me so that I can perform a backup just in case future flashing goes wrong I have a full backup to return to.
Would I be right in thinking there is no point in backing up the boot image, so I should just choose system and data? I just figured recovery can't flash a boot image anyway.
Bit confusing with the internal storage.
Thanks,
Click to expand...
Click to collapse
I understand you, I was a bit lost at first but it's pretty much the same. Take good advice that TWRP can not charge your phone in Recovery mode so make sure you have enough battery before entering Recovery. Battery level will always show 66% what ever the battery of your phone, it's known bug.
Reboot in Recovery -> select Backup -> (in Backup Device section) tick or untick what you want to preserve ( I personally do one full backup except cache and one with data only.) You can set a specific name via the Set Backup Name, once done you just have to slide the arrow button to start the backup process.
That's it, that easy.
No need to backup recovery, it stays in previous condition when you return to it in case need to
fedez1 said:
Sorry for my extreme cautiousness but I'm still researching before taking action.
Is flashing the boot.img potentially dangerous? If by accident I'll flash the wrong boot.img would I brick my device? For "brick" I mean a state where I can fix the issue only by physically opening the phone (I'm not concerned about data loss).
If the boot.img is wrong/damaged would fastboot still work?
Click to expand...
Click to collapse
Can anyone answer that?
Just to be more clear on what I'm trying to achieve; it's exactly what's explained here (for the galaxy nexus, but I thought it was possible on hox+ too):
youtube.com/watch?v=Z_5jgJe8G9k
(sorry I cannot post urls yet)
Thanks.
i would like to point out, it IS EXTREMELY HARD to brick our devices while it's S-ON, you would have to be doing really stupid stuff to brick your device with S-ON enabled.
fedez1 said:
Can anyone answer that?
Just to be more clear on what I'm trying to achieve; it's exactly what's explained here (for the galaxy nexus, but I thought it was possible on hox+ too):
youtube.com/watch?v=Z_5jgJe8G9k
(sorry I cannot post urls yet)
Thanks.
Click to expand...
Click to collapse
I guess I am having trouble comprehending why you want to do this. Just flash the recovery to the phone permanently. Or use CWM as it has no charging issues.
Lloir said:
i would like to point out, it IS EXTREMELY HARD to brick our devices while it's S-ON, you would have to be doing really stupid stuff to brick your device with S-ON enabled.
Click to expand...
Click to collapse
Sorry to be really pedantic but can you give me an example of a stupid thing that I could do to brick it? Downloading the wrong/corrupted boot.img and flashing it would brick (physical intervention required to repair) my device?
(Again sorry for asking again but I'm trying to really understand how things work. I'm a pretty experienced linux user so I would understand technical details).
---------- Post added at 12:59 AM ---------- Previous post was at 12:52 AM ----------
Kraizk said:
I guess I am having trouble comprehending why you want to do this. Just flash the recovery to the phone permanently. Or use CWM as it has no charging issues.
Click to expand...
Click to collapse
Since it's quite impossible to find the stock RUUs around, what I want to do now is to backup everything (even the stock recovery) before starting to flash anything new. Maybe what I'm trying to do doesn't make sense, can you explain me why I shouldn't care about the stock recovery? (eg: is it restored by the stock RUU before any ota update?, ...)
Also, being able to run twrp/cwm without flashing anything looks quite neat. I wonder why it works with the galaxy nexus and not with the hox+. Maybe it's somehow related to the S-ON (just a noob guess).
By flashing a boot.img of a wrong device is one example
Sent from my HTC One X+ using Tapatalk 2
fedez1 said:
Sorry to be really pedantic but can you give me an example of a stupid thing that I could do to brick it? Downloading the wrong/corrupted boot.img and flashing it would brick (physical intervention required to repair) my device?
(Again sorry for asking again but I'm trying to really understand how things work. I'm a pretty experienced linux user so I would understand technical details).
---------- Post added at 12:59 AM ---------- Previous post was at 12:52 AM ----------
Since it's quite impossible to find the stock RUUs around, what I want to do now is to backup everything (even the stock recovery) before starting to flash anything new. Maybe what I'm trying to do doesn't make sense, can you explain me why I shouldn't care about the stock recovery? (eg: is it restored by the stock RUU before any ota update?, ...)
Also, being able to run twrp/cwm without flashing anything looks quite neat. I wonder why it works with the galaxy nexus and not with the hox+. Maybe it's somehow related to the S-ON (just a noob guess).
Click to expand...
Click to collapse
Are you on the international or at&t variant. If international what country and carrier. I am almost positive I can find you an RUU to save. Also both stock recoveries are available on these forums.
Sent from my HTC One X+ using xda premium
AW: [Q] TWRP backup
fastboot is a tool with commands...
if hboot okay, phone is not bricked
Kraizk said:
Are you on the international or at&t variant. If international what country and carrier. I am almost positive I can find you an RUU to save. Also both stock recoveries are available on these forums.
Click to expand...
Click to collapse
That would be great! It's an UK Sim Free (I suppose international then), it doesn't have a specific carrier, but I'm using it with three.
I tried to follow some links for the stock RUU/recoveries but they're all not functioning.
Thanks.
---------- Post added at 09:51 AM ---------- Previous post was at 09:45 AM ----------
skdubg said:
fastboot is a tool with commands...
if hboot okay, phone is not bricked
Click to expand...
Click to collapse
That was my impression too. So probably the thing that I really need to understand is:
Code:
fastboot flash boot boot.img
is replacing hboot or some other part of the boot process? (eg. kernel/initram)
If it's replacing some other part of the boot process how flashing a broken/wrong boot.img can brick my phone? Wouldn't I be able to still use fastboot to flash a stock/correct boot.img again?
Thanks for all your clarifications.
we CANNOT even touch hboot with s-on, the ONLY thing flashing a boot.img is replacing the ramdisk and kernel. the worst that can happen if you flash a boot.img and it's corrupt or anything, you'll end up stuck at the HTC screen and forcing yourself to reboot into bootloader. FASTBOOT will be available for you to "repair" the device.
thanks
-Lloir
Hi,
Nexus 9 is my main device and I prefer to install roms without using a pc. Is there a way or tutorial to make a twrp flashable rom file out of Android M or any stock image through our tablet? I mean not using a pc at all...
I don't suppose you're rooted right now? If you are get flashify. If you're not your going to need fastboot and a pc.
Sent from my Nexus 5 using XDA Free mobile app
I am already rooted. Can flashify install the stock rom?
albsat said:
I am already rooted. Can flashify install the stock rom?
Click to expand...
Click to collapse
i can make one but you need to be on the latest bootloader
@USBhost
I will find a pc to update the latest bootloader. Please go on with the rom. Thanks.
They can fairly easily be modified into update.zip files without the "common" approach of extracting the files from the image and going through a long drawn-out process of formatting, copying, setting permissions, etc.
The key is in the updater-script file in the update.zip package. Look at the syntax around installing an "image" file, like boot.img. Now you just extend the script to do the same thing with all the other .img files, and strip out all the junk that you don't need.
This goes for bootloaders, radio, recovery, boot, system.... everything. All works the same.
doitright said:
They can fairly easily be modified into update.zip files without the "common" approach of extracting the files from the image and going through a long drawn-out process of formatting, copying, setting permissions, etc.
The key is in the updater-script file in the update.zip package. Look at the syntax around installing an "image" file, like boot.img. Now you just extend the script to do the same thing with all the other .img files, and strip out all the junk that you don't need.
This goes for bootloaders, radio, recovery, boot, system.... everything. All works the same.
Click to expand...
Click to collapse
I am not that good but I do understand your logic. I guess that is the way that @USBhost will make the M rom. Just the bootloader needs to be updated via fastboot if I am not mistaken.
It would be great to have such a zip template as someone can update the img files easy later on.
albsat said:
Just the bootloader needs to be updated via fastboot if I am not mistaken.
Click to expand...
Click to collapse
Nope. Bootloader can be updated in any manner you prefer. You can even update it from directly within android by dd'ing it to the right place(s). Google seems to like to reboot the unit right after installing the bootloader, probably because the bootloader is where fastboot is actually implemented (take advantage of any updates or bug fixes there...) BUT, this is certainly not mandatory. Remember that factory OTA's update everything from recovery!
---------- Post added at 07:52 PM ---------- Previous post was at 07:52 PM ----------
albsat said:
I am not that good but I do understand your logic. I guess that is the way that @USBhost will make the M rom. Just the bootloader needs to be updated via fastboot if I am not mistaken.
It would be great to have such a zip template as someone can update the img files easy later on.
Click to expand...
Click to collapse
EVERY update.zip that includes a boot.img *is* such a template.
doitright said:
Nope. Bootloader can be updated in any manner you prefer. You can even update it from directly within android by dd'ing it to the right place(s). Google seems to like to reboot the unit right after installing the bootloader, probably because the bootloader is where fastboot is actually implemented (take advantage of any updates or bug fixes there...) BUT, this is certainly not mandatory. Remember that factory OTA's update everything from recovery!
---------- Post added at 07:52 PM ---------- Previous post was at 07:52 PM ----------
EVERY update.zip that includes a boot.img *is* such a template.
Click to expand...
Click to collapse
i know
i would never dd the bootloader
always fastboot
USBhost said:
i can make one but you need to be on the latest bootloader
Click to expand...
Click to collapse
I'd be very interested if you could make a TWRP installable version of M.
Let's hope..
Will also be very interested.
hi,
i wanted to flash stock android (used an rom before) so i erase recovery system etc.. and when i want to flash the system img it says "
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
-.- what can i do ?
any solutions ?
thanks
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
enriquejones666 said:
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
Click to expand...
Click to collapse
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
disturbd1 said:
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
Click to expand...
Click to collapse
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
tdct12 said:
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
Click to expand...
Click to collapse
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
disturbd1 said:
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
Click to expand...
Click to collapse
Just download the newest build and fastboot flash bootloader bootloader.img :good:
oediv said:
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
Click to expand...
Click to collapse
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
enriquejones666 said:
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
Click to expand...
Click to collapse
2 people 1 idea
It's on the way, I said " want to update the OS and Made a factory reset before"
Have you tried flashing the factory images with fastboot? Pretty straight forward...
For future reference, how did you erase things with the bootloader locked?