Related
I am getting following error while trying to flash RAV1.2.0G.img on myTouch in fastboot. I have followed the
downloading 'boot.img'... FAILED (remote: not allow)
I have flashed myTouch last night using One Click with the Cyanogen_3.9.11.2_32a ROM from here: http://forum.xda-developers.com/showthread.php?t=544854
i don't think it works because you are still stuck with the perfect spl. I might be wrong on this. Not sure. Have you also checked that you put the recovery image in your fastboot location?
arunchowdhary said:
I am getting following error while trying to flash RAV1.2.0G.img on myTouch in fastboot. I have followed the
downloading 'boot.img'... FAILED (remote: not allow)
I have flashed myTouch last night using One Click with the Cyanogen_3.9.11.2_32a ROM from here: http://forum.xda-developers.com/showthread.php?t=544854
Click to expand...
Click to collapse
if you have a mytouch you have a 32B board. And yet you have installed a 32A rom.... but trying to put a 32B recovery image on..... maybe this is the cause....
next time don't start a new thread for this- post it in the thread about the recovery image: http://forum.xda-developers.com/showthread.php?t=530492&page=10
Yeh, I know i have done this a few times but you really didn't need a new post for this. there are already alot of posts and a simple search would have found. But anyway
On your device since you have used the one click method you are able to install different roms using a security loop hole of the kernal. How ever you are still running the "perfected" spl so you are not going to be able to do that using the method that you did. If you want the other recovery image on your device you will need to do the gold card method that Amon_ra had posted. It is not as complicated as it looks. but that will get you what you are looking for.
thanks for your reply, and apologize for creating burden.
All I want is quick and easy way to flash HERO ROM on my T-Mobile MyTouch device. I have tried all options flashing the recovery image. Please help!
in my opinion, do not use the one click root... use Amon_Ra's method, worked fine for me.
Ive been looking all over the forum to find a answer to this but it ive getting many different answers and dont know which one is right. My phone is a HTC Magic UK vodafone brand with a 32b board. It also has the newest 1.6 OTA update installed with the 1.33.0004 HBOOT. Ive been told that i need to downgrade to 1.5 but using the command "fastboot boot <Recovery Image>" im able to load the Amon-RA recovery. Using the recovery ive been able to create a nandroid backup but my question is if i used the recovery to wipe then install a ROM will this break the phone or do i need to downgrade first. Also could i flash the recovery image instead of just booting it.
I have the same phone as you.
I followed:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
Goto the "Non-TMobile 32B Magics" section and follow. It's what I did and it seemed to be the only way to get my phone to 1.5. You have to put it to 1.5 as 1.5 has a security hole in it to allow you to gain Root access to the device.
Thank You, i'll have read through and if i fully understand it i'll give it a go.
ive getting up to the point where it asks me to enter the command "adb push C:\recovery-RA-sapphire-v1.5.2G.img /sdcard/RA152G.img" the command says it completed successfully but the file wasnt on the sdcard. I copied the file manually and renamed it to RA152.img and entered the command from the guide "adb shell flash_image recovery /sdcard/RA152G.img", the command prompt said "flashing recovery from /sdcard/RA152G.img" and nothing after that. After resetting the phone into the recovery mode, its just the default recovery mode so it hasnt flashed correctly. Does anyone know what i should do now.
Edit: Ive tryed using fastboot but it said signature verify failure
Re-download the file, do an MD5 check on it and then flash the phone again.
MilanoChris said:
Re-download the file, do an MD5 check on it and then flash the phone again.
Click to expand...
Click to collapse
Thanks MilanoChris buit ive checked the MD5 and tryed to reflash it about 10 times.
I still havn't managed to root it yet anyone got any ideas?
The command "adb shell flash_image recovery /sdcard/RA152G.img" isn't working there is no error message but when I boot into recovery it is the original one. Does anyone know any why it hasn't actually flashed it and alternative commands I can use instead.
Edit: Also using the command "adb push C:\recovery-RA-sapphire-v1.5.2G.img /sdcard/RA152G.img" doesn't work, it says it was successful but when I check the sdcard it isn't there. Anyone know why this is.
If you haven't downgraded yet the recovery won't flash. All of the steps for non-tmobile 32B's are after downgrading. The only thing that is different is how you get the recovery flashed. Are you still having issues with the sappimg.nbh file from Cyanogen?
Thanks but how do I downgrade first as the guide on the site doesnt have a section for dowgrading non mytouch magics.
Sorry if I wasn't very clear on that! The guide is a little frankensteined for you folks using non mytouch magics. What you want to do is follow the normal procedures for downgrading. As soon as you have downgraded to 1.5 in the normal steps it's time to jump over to the non tmobile specific procedures using adb.
Hope this is a little more clear!
phantommusik said:
Sorry if I wasn't very clear on that! The guide is a little frankensteined for you folks using non mytouch magics. What you want to do is follow the normal procedures for downgrading. As soon as you have downgraded to 1.5 in the normal steps it's time to jump over to the non tmobile specific procedures using adb.
Hope this is a little more clear!
Click to expand...
Click to collapse
Thank You, I'll give it a go.
phantommusik said:
Sorry if I wasn't very clear on that! The guide is a little frankensteined for you folks using non mytouch magics. What you want to do is follow the normal procedures for downgrading. As soon as you have downgraded to 1.5 in the normal steps it's time to jump over to the non tmobile specific procedures using adb.
Hope this is a little more clear!
Click to expand...
Click to collapse
Thanks its worked but I cant get into the phone as it wont let me sign in to my google account. I have correctly entered my apn details, is there any way i can bypass it or another way to fix it.
EDIT: Doesn't matter used a different sim and it worked, Thank you again.
Phone: HTC Evo
Requirement: NAND unlock S-OFF (this allows for unsigned ROM)
Format: PC36IMG.ZIP
OS: 3.30.651.2 (2.6.32-15 Kernal)
Radio: 9.01
hboot: 2.02.0000
recovery: clockworkMod 2.5.0.1
WIMAX: 26023
PRI Version: 1.77_003
Wipes all user data: YES
Rooted: Yes
Link: http://www.megafileupload.com/en/file/278989/PC36IMG-zip.html
How to install: Download the file from the link above and and rename it from [Megafileupload]PC36IMG.zip to PC36IMG.zip. Place the file "PC36IMG.ZIP" file on the root of the SD-CARD. Power down the phone. Power up the phone while holding down the volume down button. The phone will prompt you to install a new rom, follow the prompts and reboot after flashing.
Purpose:
To create a current base rom to flash other roms without starting at the 1.47 PC36IMG.zip version.
Disclaimer: I am not responsible for any damage to your phone! Please do a nano backup prior to using this rom. This definately is a test rom, worked perfectly for myself, but not tested by anyone else. If you have any problems, boot into recovery and restore your nano backup.
Acknowledgments:
All the developers that have shared their hard work on XDA!
Note: You can unzip the file, remove the modules like ClockWorksMod or hboot then rezip the file as PC36IMG.zip to prevent those portions from being installed if you prefer.
I was just about to request this. Thanks!
Just to Clarify: (not that your directions weren't clear, just want to make sure there are no hiccups for anyone.)
The phone will scan for and find the image.
It will take a little while to load. Should have a blue status bar to the right.
Do you want to start update? Volume Up: Yes
Once it is finished: Do you want to reboot device? Volume Up: Yes
uberlemur let me know how it works for you. Like I said I only tested it on my phone. But I am confident that it will work, or I wouldn't have tried it on my own phone.
Karadorde, thanks for the more detailed instructions.
weidnerj said:
uberlemur let me know how it works for you. Like I said I only tested it on my phone. But I am confident that it will work, or I wouldn't have tried it on my own phone.
Karadorde, thanks for the more detailed instructions.
Click to expand...
Click to collapse
Yours were fine and it is pretty self explanatory, but I know doing things through HBoot can sometimes be daunting for those who have never tried it.
Just wanted to clarify if flashing this IMG with the .79 hboot will re lock Nand protection. I've used Toasts part 1&2 and yet skeptical about using unrevoked forever.
good stuff man!
Here is a picture of my Evo screen. I had used unrevoked forever prior to flashing the rom.
weidnerj said:
Here is a picture of my Evo screen. I had used unrevoked forever prior to flashing the rom.
Click to expand...
Click to collapse
The reason why I asked is that when rooting a new EVO,the radio, pri and wimax partitions get downgraded(using the traditional root method). With this, you can revert to the most current partitions all in a single flash including the Rom base instead of multiple flashes correct ??
You are correct, as long as you have ran the unrevoked forever to turn off the NAND unlock S-OFF prior to installing this ROM so that you can flash unsigned ROMs. This ROM has root built into it, so it would be just one step process to flash with this rom to have the latest of everything yet still have root.
mendez_v said:
Just wanted to clarify if flashing this IMG with the .79 hboot will re lock Nand protection. I've used Toasts part 1&2 and yet skeptical about using unrevoked forever.
Click to expand...
Click to collapse
Sounds like you will lose the Engineering HBOOT if you use this zip.
weidnerj said:
You are correct, as long as you have ran the unrevoked forever to turn off the NAND unlock S-OFF prior to installing this ROM so that you can flash unsigned ROMs. This ROM has root built into it, so it would be just one step process to flash with this rom to have the latest of everything yet still have root.
Click to expand...
Click to collapse
Thanks. My only question now is can I expect the same results if I obtained S-OFF through Toasts part 2, simple root or any other method other than unrevoked?
thanks
it worked
mobilemaniac said:
Sounds like you will lose the Engineering HBOOT if you use this zip.
Click to expand...
Click to collapse
Yep. Two different hboot.imgs. You can still take advantage of this information though. Keep your engineering bootloader but still update your radio, pri, etc.
noob here... in a bit of a bind
i did this update and it gave me this message
[5] BOOT Fail-pu
now the phone just goes to a back screen with green writing
ClockworkMod Recovery v2.5.0.1
what did i do?!?!?
peepeesea said:
noob here... in a bit of a bind
i did this update and it gave me this message
[5] BOOT Fail-pu
now the phone just goes to a back screen with green writing
ClockworkMod Recovery v2.5.0.1
what did i do?!?!?
Click to expand...
Click to collapse
Try it again.
Or if trying it again fails, you can boot into recovery and restore your nano backup. The part that failed is the system, but clockworkmod is still here.
weidnerj said:
uberlemur let me know how it works for you. Like I said I only tested it on my phone. But I am confident that it will work, or I wouldn't have tried it on my own phone.
Karadorde, thanks for the more detailed instructions.
Click to expand...
Click to collapse
The first time I tried I got a Fail-PU message for the boot partition. I'm pretty sure that's my phone's fault though, as the boot partition has been acting screwed up for days. (Not coincidentally, this is the reason I was looking for a complete PC36IMG.zip).
I flashed it a second time though, and all was well. Thanks again.
uberlemur thanks for the feedback.
Hopefully peepeesea was able to get it to work or able to restore the old nano backup...
So I guess that means that I have had 2 successful installations. LOL
will this work if you have Amon_RA recovery already?
If you're asking if we have Marshmallow, yes we do, in the form of Resurrection Remix 6 (WIP) and CM13 (WIP).
You said with locked bootloader it doesn't boot. Did you mean UNLocked bootloader? When you unlocked your bootloader, did you install TWRP?
When you installed TWRP did you wipe EVERYTHING?
If wiped everything then you have no ROM to boot. (You should have done a factory re-set instead.)
You have to go back into TWRP and drag over a ROM from your computer... install that in TWRP and then it will boot.
I'm only guessing at what you did, so that's my best answer.
_______
Oh, wait, looking at your other posts, you're the guy who re-locked his Droid Turbo bootloader and bricked it:
http://forum.xda-developers.com/droid-turbo/help/relocked-bootloader-bricked-t3306081
So, that's your issue. Still not sure why you did that. You paid for Sunshine, it was a one-time deal, can't be done again, and you still re-locked your bootloader. An unlocked bootloader is FREEDOM. You can screw up and still recover from mistakes. A locked bootloader is slavery, and if you mess up, much harder -- sometimes impossible -- to recover from mistakes...
IF that's still your issue, the only thing you can try to do is re-install stock 5.1 Droid Turbo Lollipop image via fastboot. Good luck.
This post by @TheSt33v in the other thread where you posted gave you the only possible answer. If you have TWRP still installed you have to overwrite everything, including the recovery partition. But you have to follow the steps exactly.
http://forum.xda-developers.com/showpost.php?p=65095391&postcount=5
TheSt33v said:
With a locked bootloader, it's very possible to overwrite the recovery partition with the stock recovery menu. In fact, it's possible to flash all of the stock images with a locked bootloader.
See section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684.
As for the OP's issue, I would say that if following section 0 of my guide does not solve the problem, you should probably consider your phone destroyed.
Click to expand...
Click to collapse
Hi,
I want to know if it is possible to relock the bootloader and get the drm back?
I backup the TA partition before unlock my bootloader
Thanks in advance
You followed the last link in point #2 on https://forum.xda-developers.com/showpost.php?p=70504721&postcount=2 ?
Hint: read the thread. one answer is in post #20
DHGE said:
You followed the last link in point #2 on https://forum.xda-developers.com/showpost.php?p=70504721&postcount=2 ?
Hint: read the thread. one answer is in post #20
Click to expand...
Click to collapse
I read it yes. But I was thinking at something :
I have a battery issue, after one day of use, I have to recharge it. Could it be the cause of the unlocked bootloader ? Or the stock ROM ?
Other things, I was trying to flash superSU via TWRP but I have a password to enter when I open TWRP to decrypt data. After cancel this step, I flash the superSU zip, and then I brick my phone. I have to boot in flashmode to flash via flashtool. I try 2 superSU zip and always the same problem.
For you, is it better to re-lock the bootloader (hard step for me, regarding the #20 on the thread) of find a solution for my TWRP/root problem and then flash another custom ROM ? (If option 1, any ideas about this problem ?)
Thanks in advance
nathan30 said:
I read it yes. But I was thinking at something :
I have a battery issue, after one day of use, I have to recharge it. Could it be the cause of the unlocked bootloader ? Or the stock ROM ?
Other things, I was trying to flash superSU via TWRP but I have a password to enter when I open TWRP to decrypt data. After cancel this step, I flash the superSU zip, and then I brick my phone. I have to boot in flashmode to flash via flashtool. I try 2 superSU zip and always the same problem.
For you, is it better to re-lock the bootloader (hard step for me, regarding the #20 on the thread) of find a solution for my TWRP/root problem and then flash another custom ROM ? (If option 1, any ideas about this problem ?)
Thanks in advance
Click to expand...
Click to collapse
I really doubt you read my post or understood it or made some effort to follow the links I provide (your repeated questions here of obvious issues all handled there).
I recommend you reset/complete wipe your phone in TWRP. Delete everything except SD-Card.
Then flash a stock SONY ROM via FlashTool. Then relax and enjoy for some days.
Check if you are really allowed to unlock your phone and if check if it is unlocked (all in my long post!).
I wrote "NEVER EVER ..." Did you read this? Your problems could stem from the enbling of MyXperia. Then you might be even beyond repair...
If you still want to root the phone - print my long post and proceed one step after the other and make some remarks on the progress on the printout.
What you write here could (besides MyXperia) also be the problem that you did not follow the steps and flashed SupeerSu before the custom kernel.
I am getting tired of this ...
DHGE said:
I really doubt you read my post or understood it or made some effort to follow the links I provide (your repeated questions here of obvious issues all handled there).
I recommend you reset/complete wipe your phone in TWRP. Delete everything except SD-Card.
Then flash a stock SONY ROM via FlashTool. Then relax and enjoy for some days.
Check if you are really allowed to unlock your phone and if check if it is unlocked (all in my long post!).
I wrote "NEVER EVER ..." Did you read this? Your problems could stem from the enbling of MyXperia. Then you might be even beyond repair...
If you still want to root the phone - print my long post and proceed one step after the other and make some remarks on the progress on the printout.
What you write here could (besides MyXperia) also be the problem that you did not follow the steps and flashed SupeerSu before the custom kernel.
I am getting tired of this ...
Click to expand...
Click to collapse
Hi, and thanks again for your patience and help. You're right, I've missed the kernel part, before flash SuperSU. I'll read again you're post and follow instructions step by step.
Thanks again, and sorry for this :/
DHGE said:
I really doubt you read my post or understood it or made some effort to follow the links I provide (your repeated questions here of obvious issues all handled there).
I recommend you reset/complete wipe your phone in TWRP. Delete everything except SD-Card.
Then flash a stock SONY ROM via FlashTool. Then relax and enjoy for some days.
Check if you are really allowed to unlock your phone and if check if it is unlocked (all in my long post!).
I wrote "NEVER EVER ..." Did you read this? Your problems could stem from the enbling of MyXperia. Then you might be even beyond repair...
If you still want to root the phone - print my long post and proceed one step after the other and make some remarks on the progress on the printout.
What you write here could (besides MyXperia) also be the problem that you did not follow the steps and flashed SupeerSu before the custom kernel.
I am getting tired of this ...
Click to expand...
Click to collapse
So, here I try to re flash TWRP properly. I re flash latest Nougat with FlashTool (wipe APPS_LOG and USERDATA and exclude CUST_RESET and FOTA_RESET) to start clean. Then I flash AndroPlus kernel v19 with
Code:
fastboot flash boot boot.img
. After I flash latest TWRP and flash it with
Code:
fastboot flash recovery twrp-3.0.2-0-kagura.img
. I can access to recovery with POWER and VOL - (I can access, unless you said we can be stuck at this point) and I always have the ask for a password to decrypt data. What is wrong now ?..
use the LATEST TWRP
https://drive.google.com/drive/folders/0B0j3VJ1Xp5N8Y1FZSmMwM1BOZDQ