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
Related
i installed a custom rom, after that my phone is not booting, stuck on htc white page, i tried to do factory reset and restore NAND backup, am getting error msg, and format aborted.
WHAT SHALL I DOOO PLZ HEELLPPPP....
What hboot do u have?
darkylight said:
i installed a custom rom, after that my phone is not booting, stuck on htc white page, i tried to do factory reset and restore NAND backup, am getting error msg, and format aborted.
WHAT SHALL I DOOO PLZ HEELLPPPP....
Click to expand...
Click to collapse
Being stuck on the HTC white splash screen generally indicates there is an issue with the currently loaded kernel. Essentially, the currently loaded kernel is not compatible for any number of reasons.
Depending on your "unlock" method, there are two methods to restore/load an alternative kernel.
1) If using the HTC unlock method, fastboot mode will have to be used to load a different kernel.
2) If using the Revolutionary unlock method, the traditional custom recovery mode should allow a different kernel to be loaded.
There are lots of guides posted all around on how to recovery in both of these situations, but if you need more guidance, post back which unlock method was used.
Hope that helps!
mugetsu666 said:
What hboot do u have?
Click to expand...
Click to collapse
1.49.0018.
plz help me i just wanna make it booot..
well it might be kernel but how could i fix it.
i used this method :"http://forum.xda-developers.com/showthread.php?t=1225974" for unlocking, and i tried to reinstall recovery but same problem..
i just need to make a factory reset and i can restore nand back up, i cant make this factory reset
plz help meeeeeee, am really desperate
joeykrim said:
Being stuck on the HTC white splash screen generally indicates there is an issue with the currently loaded kernel. Essentially, the currently loaded kernel is not compatible for any number of reasons.
Depending on your "unlock" method, there are two methods to restore/load an alternative kernel.
1) If using the HTC unlock method, fastboot mode will have to be used to load a different kernel.
2) If using the Revolutionary unlock method, the traditional custom recovery mode should allow a different kernel to be loaded.
There are lots of guides posted all around on how to recovery in both of these situations, but if you need more guidance, post back which unlock method was used.
Hope that helps!
Click to expand...
Click to collapse
Then like the person before me said just flash ur kernel and try that first
mugestsuu666, am a very newbee plz help.
how to flash the kernel ur saying?
my problem is that:
am unable to install any custom rom or restore my defaul rom, even am unable to make factory reset, or wipe date (from recovery mode).
i tried to reinstall recovery but same problem.
can u help me plzzzz.
step by step. and in details.
thanks in advance
mugetsu666 said:
Then like the person before me said just flash ur kernel and try that first
Click to expand...
Click to collapse
It could help to know what recovery you're using. Is it Clockworkmod, Team Win Recovery Project, or something else? Make sure you have your recovery set to skip MD5 sum verification.
Also, the kernel is what drives the backbone of the phone; Chad Goodman has a chart that might help you in the first post of this thread.
You could also try flashing the stock ROM to see if that helps (sorry for the lack of a link, I'm short on time).
And don't worry too much, chances are in your favor that you didn't brick your phone; it's pretty hard to do thanks to HTC.
Also, if you have used HTC Unlock, try the fastboot command 'fastboot boot (file name of your recovery image)'. So, for example if the filename was "revovery.img", your command would be "fastboot boot revovery.img". Then try and wipe your phone/ install ROMs.
million thankz
ill start working.
hope i will succeed.
I Slap Fat Kids said:
It could help to know what recovery you're using. Is it Clockworkmod, Team Win Recovery Project, or something else? Make sure you have your recovery set to skip MD5 sum verification.
Also, the kernel is what drives the backbone of the phone; Chad Goodman has a chart that might help you in the first post of this thread.
You could also try flashing the stock ROM to see if that helps (sorry for the lack of a link, I'm short on time).
And don't worry too much, chances are in your favor that you didn't brick your phone; it's pretty hard to do thanks to HTC.
Also, if you have used HTC Unlock, try the fastboot command 'fastboot boot (file name of your recovery image)'. So, for example if the filename was "revovery.img", your command would be "fastboot boot revovery.img". Then try and wipe your phone/ install ROMs.
Click to expand...
Click to collapse
Sent from my X10i using xda premium
Hello all,
I had the CWM installed, and my phone died when I was asleep, down to 0%.
Now, it won't charge. I got a half charged battery in today, so I'll be able to do some things.
The phone is S-off.
Anyways, I would like to know how I would be able to:
-Remove CWM
-Recovery EVERYTHING to factory default
Also, I'm kind of a noob, so when it comes to telling me to let's say "flash amonra", please tell me how, or link to thread or something. If you can.
All help is appreciated...If I don't get this fixed I won't have a phone for a couple years.
Also, a tip: HTC Keeps track of those who unlock the bootloader on their phone, and tell Verizon. Which is how they find out even if you reflash, relock, etc.
First thing to do is get rid of that recovery! Soo many issues and you can use either the TWRP 2.1.1 recovery or AmonRA 3.15 (located in the dev threads). CWM causes phone charging issues (as you are aware) and I recommend not using it.
Are you familiar with flashing a recovery in fastboot? Were you running GB or ICS firmware?
I suggest you familiarize yourself with all the root lingo contained in this thread.
http://forum.xda-developers.com/showthread.php?t=1641670
Marcismo55 said:
First thing to do is get rid of that recovery! Soo many issues and you can use either the TWRP 2.1.1 recovery or AmonRA 3.15. CWM causes phone charging issues (as you are aware) and I recommend not using it.
Are you familiar with flashing a recovery in fastboot? Were you running GB or ICS firmware?
Click to expand...
Click to collapse
I believe you would use the command "fastboot flash recovery [file].img".
I wasn't running the IceCreamSandwich update, pretty sure of that. So it must be the GB. I would like to know how to remove the CWM.
QuintonS said:
I believe you would use the command "fastboot flash recovery [file].img".
I wasn't running the IceCreamSandwich update, pretty sure of that. So it must be the GB. I would like to know how to remove the CWM.
Click to expand...
Click to collapse
Yes that command is correct you just have to make sure the recovery file is in same folder as your fastboot.exe.
AmonRa recover is here http://forum.xda-developers.com/showthread.php?p=19205213
Sent from my ADR6425LVW using Tapatalk 2
Well, I fixed it. Or at least it seems. All I had to do was flash the latest RUU (which was actually the currently installed rom on my phone).
Well, hopefully clockworkmod is GONE.
QuintonS said:
Well, I fixed it. Or at least it seems. All I had to do was flash the latest RUU (which was actually the currently installed rom on my phone).
Well, hopefully clockworkmod is GONE.
Click to expand...
Click to collapse
CWM was great on my Incredible...but I've had the same problem you did with charging issues, not to mention backups that would freeze in mid stream.
Flashing a RUU was the only way I could find to fix it.
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
ten6 said:
Was running NRG GB just fine. When giving the phone to the wife I decided to upgrade to ICS. Used CWM to wipe data, cache, etc, and installed, got freeze on HTC logo. Started using Superwipe before each try and also tried flashing several different kernels including the one inside the zip and the one included with the amaze stock kernel flasher. Now the best I can get is 5 seconds into the Energy spinning rings logo before a 5s freeze and reboot.
The only thing I haven't tried is firmware; I've seen references to "find it on the forums" but copious forum and google searches don't seem to lead to the ICS firmware itself. Can anyone help with that or point out what I'm forgetting?
In the meantime I will try installing the ICS stock ROM first and see where that gets me.
Click to expand...
Click to collapse
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Dark Nightmare said:
Do just that, remember to lock your bootloader if you're s-on and yes, jumping to an ICS rom without updating your device caused the bootloop.
Click to expand...
Click to collapse
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
ten6 said:
Thanks for the reply! I'm downloading PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip from filefactory, it's taking forever. Am I flashing this with CWM? Or should I be downloading a GB factory ROM and using that instead, then re-locking the bootloader and trying to update over the air?
Click to expand...
Click to collapse
Don't download that one, it has issues, hold up, I'll give you a link to the most recent file.
Here, get this: http://d-h.st/3VD
Download speed should be faster as well. rename it PH85IMG and place it on your sd card after you relock your bootloader, then boot into bootloader, it's gonna detect the file and ask you if you wanna update, follow the on screen instructions to update, voila! Follow the basics to install the new energy rom.
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
It's almost as tho NO One reads anymore. It's actually getting kinda ridiculous how many times the same issue is gonna be asked.
I know this post isn't very helpful but I'm sure most of the recognized/senior/not noobs members are getting frustrated.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It is useful, I fully agree with you, it's like we come here to answer the same questions over and over, but I'm just trying to be nice, cause I usually just say, read the amaze bible, but then they go and do something even more noobish, so to avoid the tear jerks I just give the basic info, though I'm fading away slowly.
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
I came across this issue. As earlier posts said, install the new ICS update. The partitions were messed up and the ruu will clean it up.
ten6 said:
Thanks'd for the link and the help. I was gonna get mad about being called a noob who can't read, but I guess it's a small price to pay for instant, free help. Keep on rockin' XDA.
Click to expand...
Click to collapse
Lol, never pointed fingers buddy, so calm down.
Maybe I should create a new topic but my issue is similar to this one except for the fact that I read quite a lot and tried quite a few things.
My situation is that I made a backup with cwm only booted not flashed so I have the 100% stock backed up, after this I flashed cwm and tried to install the Energy rom based on ics and that was my mistake as I used to be on a Nexus device I didn't have to worry about this.
So I got stuck on a bootloop and tried factory reset/wiping everything, tried to reinstall a stock ROM (t-mobile one as I only found a .exe for the videotron one and I did not feel like exploring the exe as I am a Linux user) by relocking bootloader and using the HTC method, tried to install manually the stock Kernel with Energy ROM using adb and fastboot commands, tried to restore my backup but nothing seems to work, I'm still bootlooping.
Is-it possible to s-off without a regular adb access (only the cwm adb access)? And would s-off allow me to flash anything as I wish? Is there a way to have any ROM working on my device? (i know the answer is yes to the last one, at least )
Thanks!
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
It's Better To Fail At Originality
Than To Succeed In Imitation.
-Mighty Healthy
Click to expand...
Click to collapse
Double0EK said:
Edited: I don't know why I even replied to the post above this.
Read more you'll find out what you're doing wrong.
~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
johnride said:
Maybe I'm a noob on this forum but it's far to be the first time I face a problem in software configuration/installation and I read quite enough (spent about five hours on xda, google, etc.) to say that you should at least help me a bit by linking me to a thread where I can find an answer.
I know my mistake was to install ics at first but now I flashed the stock recovery back, I relocked the bootloader via fastboot and put the file on the root of my sdcard renamed correctly that it be detected automaticly (and it apparently does install) but I still got the * bootloop.
I'm able to read a manual and to read the Amaze 4G bible four times to try to point out the detail I forgot. I made my homework and now it would only be nice from you that you help me a bit...
Click to expand...
Click to collapse
Okay okay, calm down, there's currently only one method of going about restoring your device since you're s-on and no you cannot s-off with just cwm adb, I think JB s-off method is only an exe file, never saw linux files anywhere on his site. Anyways, you have to use the GB exe for videotron and restore to stock via it then update to ics to use the most recent energy rom, BUT if you just want a working device, this is just an idea, though it should work fine, you can flash a custom recovery and flash the GB version of energy rom, you should be able to restore your backup as well, but you said you can't, which is odd, it may be because of the kernel not being flashable as since CWM cannot flash kernels while s-on, in which case I'd advise you to get 4EXT recovery and then try restoring your back once again, it should work fine since 4EXT can flash kernels while S-ON.
My two cents.
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
johnride said:
Well, 4ext doesn't works, apparently it flashes correctly but I can't boot in it so can't even try to restore my backup, s-off doesn't works from cwm and my device has to be booted to work with Videotron's exe (or I badly installed my drivers, I nerver understand properly the 899363 drivers per device I have to install for an android phone on Windows?)
Smells bad... I checked the 4ext's md5sum and it's alright, I took it from the fastboot installable img in direct dl from the thread in the Amaze bible.
Any idea?
Oh and there is a JB s-off executable for Linux on his site. After all I guess it is mostly adb commands?
Click to expand...
Click to collapse
I got lost halfway through that post, after flashing a rom, if the kernel isn't flashed (reboots and does it automatically), then flash the kernel manually, should boot fine, does anyone ever really read anymore? This very issue both s-on and s-off has been answered more times today than I can count. If you read the details on JB's site, you'd see and know all you need to.
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
johnride said:
Right, I'va already flashed manually the stock kernel as sais in the NRGRom thread without success before my first post here, will look at different kernels.
Click to expand...
Click to collapse
How did you go about flashing the kernel?
Sent from my SGH-T679 using xda app-developers app
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
johnride said:
There was a flash.sh file in the zip with the kernel, I couldn't run it normally as I can't boot but I went in cwm (maybe I should have used 4ext, don't think so for this part) executed the adb commands there were in the sh file with all filesystems mounted, rebooted into fastboot and flashed the kernel image. Maybe there are differents /system when in cwm and when booted on regular system... Will figure that out when I have time to spend on this, as soon as possible.
Thanks for all the cues!
Sent from my Nexus S
Click to expand...
Click to collapse
Okay here's a few tips, cwm cannot flash kernels with son devices, get 4ext recovery for that. Second thing, reflash the from after doing a super wipe, if 4ext doesnt reboot and flash the kernel, do it manually, ill assume you know how to use ad, if not check my Bible tutorial on it, use the boot command for flashing boot images, take the boot file from the zip file, place it in the folder where your adb files are and flash it to your device while its in fastboot mode.
Sent from my SGH-T679 using xda app-developers app
Well, I think I have done all you mention above, the only thing i'm not sure to understand is what you mean by "super wipe" I found some executables about it but I guess it can't do much more than the flash all partitions (except external sdcard) in 4ext recovery wich I finally managed to install properly.
So, I made that global formatting thing, I tried to install an ICS based ROM and 4ext rebooted to install kernel, same bootloop. Tried to install manually the kernel that came with this rom via the classic fastboot flash boot boot.img. Same bootloop. Tried to put the modules manually via the recovery adb access (performing a mount -a in adb shell to have everything present in fstab mounted) and flashing this stock kernel with no more success.
Achieved the same operations with a GB based ROM (this one: http://forum.xda-developers.com/showthread.php?t=1535173) with both the faux and the stock kernel without any more success.
Did I miss something? Am I so dumb? Do you have any other rom to suggest that have higher chances to succeed?
Do you think trying to restore my sotck nandroid with 4ext has more chances to succeed?
Thanks, again and always!
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
The title says it all. My M8 has the bootloader unlocked, it's S-off and rooted with Teamwin recovery installed. I started dicking around with it, and messed it up. I went to HBOOT and factory reset. I now have no OS, so obviously, my phone won't start up. I appear to be really stuck. If you guys help me and talk me through this, I'll stop dicking around. :-/
Also, I would like to load my stock bootloader, 1.12.502.18 (CID CWS__001). I've found the kernel source code as well as a 1.3 GB file from here http://forum.xda-developers.com/showthread.php?t=2701376 that supposedly houses this Nandroid backup, but I have no idea how to use it. God, I feel stupid.
Ok. I got the Nandroid backup recovery.emmc.win file pushed to the phone. Now, I have a red triangle in the middle of the screen and I can't get to recovery or fastboot.
Flash twrpCopy the rom to where your adb and fastboot are located connect phone via twrp run this command
adb push nameofrom.zip /sdcard/. exactly as shown here change nameofrom.zip to the name of the rom your trying to flash...this will put a rom on your internal storage and it then can be flashed via twrp
Wonders_Never_Cease said:
Flash twrpCopy the rom to where your adb and fastboot are located connect phone via twrp run this command
adb push nameofrom.zip /sdcard/. exactly as shown here change nameofrom.zip to the name of the rom your trying to flash...this will put a rom on your internal storage and it then can be flashed via twrp
Click to expand...
Click to collapse
I was able to get into TWRP just fine. When I pushed the file, it moved the file, but I can no longer get to TWRP. So the ROM is there, I just can't access it. Thoughts?
Ok, I got Recovery going. I'm now in TWRP. Where did adb stick the file I pushed?
take out sdcard if using one and only use internal storage..Have to push a flashable rom zip not nand backup.once is pushed it should take awhile,youll go to install like any other custom rom from the install menu. Or if you cant get that going use adb sideload command
Make sure command is correct
adb push nameofrom.zip /sdcard/.
Dumb question. Where in the world do I find the stock recovery zip? I can't find any zip...only img, etc.
You dont need stock recovery right now follow instructions to get a rom back on the device first...download any custom rom and follow what i said
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Guy in my rom thread had basically same issue hes back up and running by following what ive told you
Wonders_Never_Cease said:
You dont need stock recovery right now follow instructions to get a rom back on the device first...download any custom rom and follow what i said
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Guy in my rom thread had basically same issue hes back up and running by following what ive told you
Click to expand...
Click to collapse
Thanks for the help. Downloading your ROM now.
If you can get in recovery choose the option "adb sideload" put the ROM on your desktop and name it rom. Then in a command window type adb sideload rom.zip , TWRP will automatically recognize the update script and flash it for you.
Sent from my HTC One_M8 using Tapatalk
I took the direction of Wonders_Never_Cease and followed it to the letter. FUBAR no longer. Though I did panic a little, I learned a lot from this direction going forward. Thanks, Wonders_Never_Cease. Thanks also to everyone else who offered help.
Glad it all worked out for you...
ImNraged said:
I took the direction of Wonders_Never_Cease and followed it to the letter. FUBAR no longer. Though I did panic a little, I learned a lot from this direction going forward. Thanks, Wonders_Never_Cease. Thanks also to everyone else who offered help.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Glad it all worked out for you...
Click to expand...
Click to collapse
Not so much. I've run into another problem while trying to get it back to where I want it. SD Card will not mount. What can I do?
Aaaaand, nevermind. Youtube was my friend in this case.
Wonders_Never_Cease said:
You dont need stock recovery right now follow instructions to get a rom back on the device first...download any custom rom and follow what i said
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Guy in my rom thread had basically same issue hes back up and running by following what ive told you
Click to expand...
Click to collapse
I don't think he was asking that. I am pretty sure he was asking where he managed to find the stock recovery, which is why the red exclamation, probably because he didn't pull or nand the recovery as a raw or img file before flashing something custom (the user that asked, that is).
I doubt is is a stock AT&T ship recovery from an RUU dump or ota, since there haven't been any for AT&T that I know of yet, so it's likely just a raw dump or was part of the nand backup he restored.
Already been sorted thank you fot you insight
GSLEON3 said:
I don't think he was asking that. I am pretty sure he was asking where he managed to find the stock recovery, which is why the red exclamation, probably because he didn't pull or nand the recovery as a raw or img file before flashing something custom (the user that asked, that is).
I doubt is is a stock AT&T ship recovery from an RUU dump or ota, since there haven't been any for AT&T that I know of yet, so it's likely just a raw dump or was part of the nand backup he restored.
Click to expand...
Click to collapse