Related
Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?
Have you tried one of the Odin one clicks, it can be found here... http://www.androidaddicted.com/firm...lc4-ics-4-0-3-leaked-firmware-update-576.html
Sent from my SGH-I727 using Tapatalk 2
worias said:
Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?
Click to expand...
Click to collapse
There is no pit for the skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
There is no pit for the skyrocket.
Click to expand...
Click to collapse
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Great news! Glad you're back up and running.
worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium
cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
i dont/never used adb, can u post the commands(step by step) so i can put it in the 1 stop sticky
worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
to confirm, u didnt use adb to flash the pit file, you used odin to flash the pit file and used the pit option in odin, then you picked pda option for the stock firmware, more details u give the better so i can add it to the sticky
cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
Cool, thanks!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Yes please vinvom put it in your stickies, it'll help a lot of us.
Sent from my SGH-I727 using xda app-developers app
cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can
cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Sent from my SAMSUNG-SGH-I727 using xda premium
stoopendis said:
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Click to expand...
Click to collapse
Yes, celox.pit (extracted from the zip) is the actual pit to flash in ODIN. It's from an SGH-I727 and should be the same for Rogers version. Not 100% sure if it's the same for TMO flavor.
vincom said:
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can
Click to expand...
Click to collapse
k in going to use this thread to link from the sticky and also add it in the odin troubleshootibg section in restoring to stock
********************************************
when trying to flash stock firmwares and/or recoveries and it hangs at "Getting PIT for mapping" or getting pit errors in odin, download celox.zip and "unzip" the file, select the extracted "celox.pit" file in the pit option for odin, with all other options unchecked hit the start button in odin, once flashed you can then flash the stock firmware and/or recovery in odins pda section.
thanks cschmitt
Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.
cschmitt said:
Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.
Click to expand...
Click to collapse
k, i reedited the post
stoopendis said:
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I used the attachment from cschmitt, extracted the PIT file from the zip and then used ODIN to flash it. I was then able to flash a Skyrocket Stock ODIN tar to restore to GB and boot the phone. I have since been able to get it rooted, CWTouch on it, and have CM10 running on it well.
Thanks again everyone.
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1) .
I just tried other laptop to use Odin & stock 4.0.4 to flash back Stock rom.and got getting mapping pit....I still can go to Download mode but I can't flash anything.
Please help . Thank you very much.
If I understand, you're trying to flash 4.0.4 with odin. And it's a md5 file, right? Keep trying it. Sometimes it takes more than one try.
And check the check sum of the stock rom file you downloaded it could be a bad download
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
Lately, many people, including myself, have been at a disadvantage of not having an official RUU for JellyBean so that stock environment can be achieved. Although sometimes, OTA's are available which can do the job. Hence this Tutorial. Also this saves the effort to do S-OFF/SuperCID which often brings along more problems.
This Tutorial, in principle, can be applied to both S4 and S3 variants.
All thanks to @xander1993 at the VilleC2 Development Section who created the original thread Here. Though somewhat unclear and related to VilleC2, I thought of making a thorough guide for Ville with some minor changes.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For T-MOBILE UK Users: (UK people with other operators e.g Three, Vodafone etc can also try the Jellybean Nandroid backup IF their firmware is upgraded to that of Jellybean)
ICS Users: Those stuck on ICS custom ROMs and can't get stock, Use This RUU to get to stock ICS and then update to Jellybean via System Updates Check. Thanks to @ppm48
Jellybean Users:Those stuck on Jellybean custom ROMs wanting to get stock, I have a Stock Jellybean 4.1.1 Nandroid backup for you guys Here Since there isn't any OTA.zip for T-Mobile UK for Jellybean. You can just flash this Nandroid right away without using this tutorial. Again, Thanks to @ppm48 for this. Also, if you have bootloops after restoring this backup, flash a Jellybean Sense boot.img.
Additionally refer to this post by @mkoev , should prove a lot helpful. Then you can follow the tutorial.
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
For OPTUS Users with CID OPTUS001: (All thanks to @salac)
Get the modified OTA.zip Here. by @salac
salac said:
Follow the instructions from step 12.
Step 14. Flashing the firmware.zip worked the second try for me
Step 22. I did flash the boot.img to make sure it will work since I don't think I had the original one.
Good Luck
Click to expand...
Click to collapse
Optus users please follow @salac 's post above to flash the OTA.zip
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Pre-requisites:
1. Notepad++
2. 7-Zip (Recommended)
3. ADB+Fastboot (Get it Here)
4. HTC drivers (Standalone OR HTC Sync Manager Drivers)
5. Unlock_code.bin from HTCDev to unlock bootloader.
6. Any OS (Custom/Stock) present on the phone. (I have not tested it for phones without any OS, you may try it at your own risk and post results here) Not Needed anymore.
Common Steps:
In this guide, I will ask you to go to fastboot/adb so you should know how you would do that. (All fastboot/adb commands are to be given via Command Prompt from PC)
To execute Fastboot Commands:
- Go to fastboot folder on your PC
- Go to fastboot via bootloader on your phone
- Connect the Phone to PC and on the Phone it should say Fastboot - USB Mode
- Now in the fastboot folder on your PC, Hold Shift + Right-Click and click Open Command Window Here
- Now you can enter commands given in the guide for fastboot.
To execute ADB Commands:
- Same procedure except that you don't need to go to fasboot on your phone. You can execute adb commands while in Android OS/desktop.
To boot into Bootloader:
- While the phone is turned off, Press Volume Down + Power Button simultaneously.
OR
- If you are in Android OS, use the following adb command to boot into bootloader:
Code:
adb reboot bootloader
OR
- If you want to reboot into bootloader from fastboot:
Code:
fastboot reboot-bootloader
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Caution for SuperCID users: Please click the CROSS button on your Browser Tab, as flashing this is not intended for you. Either don't flash the OTA.zip, which will brick your phone if you do, OR change your CID to original one. e.g. H3G__001, BM___001, ORANG001
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Procedure:
- ** - ** - ** - Make Nandroid Backups before you do anything, remember you are doing this at your own risk - ** - ** - ** -
1. Download a OTA.zip – Most likely from Here. (You can rename the OTA file which usually has a long name to simply OTA.zip for ease)
2. Extract firmware.zip from OTA.zip. Then extract boot.img from firmware.zip. For now, copy Boot.img to ADB+Fastboot Folder..
3. Now to match the CID of your phone. You can get the CID of your phone via CID Getter from Play Store. Once opened, at the top will be your CID in Red color.
Alternatively, You can also get CID of your phone via Fastboot. Command for that is:
Code:
fastboot getvar cid
and it should display your CID.
4. Inside firmware.zip, look for android-info.txt. Supported CIDs should be mentioned inside this file. If it matches with that of your phone, Proceed otherwise stop and don't put yourself into more problems. (CID Match Exception: This 4th step may not be applicable to you if & only if you are to skip steps 11 to 16, if this is the case, you may flash OTA.zip skipping steps 11 to 16; Read step 10 for more info and then come back here)
5. We need to remove some code lines from inside the OTA.zip. For this, Open the OTA.zip with 7-zip (Right-click ---> 7-zip ---> Open Archive).
6. Head over to META-INF\com\google\android and find a file named updater-script. Drag it out of the archive to the folder/desktop where you can edit it. You should make an extra copy of this file.
7. Once you drag it out, delete the original updater-script inside the archive. It will recompress OTA.zip.
8. Edit with Notepad++ the extracted updater-script file. Find these lines (in the beginning of the file) and delete them altogether:
Code:
[COLOR="Purple"]assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"BM___001") == "t");[/COLOR]
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PJ4011000") == "t");,
assert(check_mid("simple", "PJ4011000") == "t");
);
You should delete these lines up to exact semi-colon ; at the end. (the purple lines with different CIDs can be different from those mentioned here, so no need to panic, just delete them)
9. Once edited, Copy this edited updater-script into the OTA.zip archive at the same location from which it was removed. It will recompress OTA.zip. You may now transfer OTA.zip to your SD-Card on your phone.
10. If you previously updated to JellyBean via OTA (Or if you have the exact or newer firmware on your phone than that present inside OTA.zip), skip steps 11 to 16. For example, if you have HBOOT Version 2.15.0000/2.13.0000 or above, it means you have already upgraded to Jellybean firmware so no need for Steps 11 to 16.
In case, if you are to proceed to step 11, that is if you are to flash firmware.zip, make sure to match CID as mentioned in step 4 to avoid any bricks. This is especially useful for those who have ICS and want to get stock JB or those on JB but want complete stock HBOOT, recovery etc.
11. Place firmware.zip extracted from OTA.zip inside ADB + Fastboot Folder.
12. Lock the bootloader, if unlocked. For this, go to fastboot on your phone and give the command:
Code:
fastboot oem lock
The phone reboots after this.
13. While in Android OS/Desktop, fire up Command window on PC to give the following ADB command to boot into OEM Update Mode.
Code:
adb reboot oem-78
OR (if you can't access OS to execute adb)
From Fastboot:
Code:
fastboot oem rebootRUU
You should be seeing HTC logo.
14. While in OEM Update Mode, give the following fastboot command to flash firmware:
Code:
fastboot flash zip firmware.zip
If it fails with error and doesn't show any Green Progressbar, keep trying the above command. Usually works after a few tries.
********** DO NOT REBOOT MANUALLY UNTIL IT FINISHES FLASHING FIRMWARE OR YOU'LL BRICK YOUR PHONE *************
15. Once firmware is updated, reboot into bootloader. Go into fastboot.
16. Place Unlock_code.bin inside ADB + Fastboot Folder. Use the following fastboot command to unlock your bootloader again. (This will wipe your phone except for SD, so you must make a backup before doing this)
Code:
[COLOR="Blue"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
17. Download a recovery. Preferred Recovery is TWRP 2.3.3.0 and I have not tested this guide with any other version. Put the recovery in the ADB + Fastboot folder.
18. Now go into bootloader again. This time to flash the recovery anew.
Code:
fastboot flash recovery recovery.img
19. Now go to the recovery via bootloader. Wipe data/factory reset, cache, dalvik.
20. Restore the Nandroid backup you had made earlier.
21. Now Flash the OTA.zip which is on your SD-Card. It should flash fine.
22. Go to fastboot via bootloader. We are now going to flash kernel with the following command, boot.img you had earlier copied to ADB+Fastboot folder.
Code:
fastboot flash boot boot.img
23. Reboot to the OS and you should see complete stock JB OS.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Please Rate the thread and Hit the Thanks button if this tutorial helped you!
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
The problem I am running into is that the best OS X alternative to 7zip is an app called BetterZip with wich the recompressed OTA.zip is of different size compared to the original (633MB vs. 647.3MB).
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Well, When I edited OTA.zip, it was the same size before/after. But maybe OS X uses different compression values.
I think you should go ahead with it and try it.
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
mortek said:
I am trying to use your method to get back to stock instead of the RUU method since I am on Mac.
.......................
Do you think this is likely to cause problems when flashing the modified OTA.zip?
Click to expand...
Click to collapse
Can you use Winzip/Winrar? Might want to check with those two..
mortek said:
I am stuck.
Since my phone is bricked and it can't boot into the ROM I cannot issue the ADB command from step 13 while in fastboot :/
Click to expand...
Click to collapse
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
khan.orak said:
last time you flashed was a Viper rom I think. So What firmware did you flash? if it was that of JB firmware then it's ok to skip the Firmware Flashing steps.
Edit: I have updated step 13. If you can't use ADB, use the fastboot command.
Click to expand...
Click to collapse
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
mortek said:
The OTA.zip was flashed successfully but in the recovery's log there is a line which reads "E:unknown command [firmware]".
The last ROM i flashed was indeed ViperRom but I didn't flash any firmware manually. Should I have done so? I didn't see such an instruction in the respective thread.
Edit:
I just saw your edit. I'll try the fastboot command and report back asap. Thanks.
Click to expand...
Click to collapse
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
khan.orak said:
Actually, I had read your post where you mentioned that you used AOSP firmware. Maybe that is a bit different than the stock firmware. If it poses problems, you might need to flash the stock one, present inside OTA.zip.
Also flash the stock kernel if you find that the ROM is behaving oddly.
Click to expand...
Click to collapse
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
mortek said:
The fastboot command worked fine so I flashed the stock firmware and the stock kernel, flashed the OTA.zip, rebooted and I am again stuck in a bootloop :/
Might be the OS X recompression. I will try again with different options.
Most likely the solution should be to get stock recovery, perform a "clear storage" command and then resume flashing. Problem is I am not aware of an alternative to the RUU method for that.
Click to expand...
Click to collapse
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
khan.orak said:
Hmmm that's strange.
I had read somewhere that formatting SD card with Stock Recovery corrects some problems while using SD.
Stock Recovery is present inside firmware.zip by the name of recovery.img. might want to flash it and clear storage. Stock recovery can be flashed using the same method as custom recovery. Refer to Steps 17,18 to flash it.
Click to expand...
Click to collapse
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
mortek said:
I flashed the stock recovery but I am still having bootloops with the stock ROM
Although, I flashed Viper rom and after several reboots it finally booted!
The truth is that I am not sure the sdcard won't get corrupt the next time my phone reboots, but its better than having a bricked phone.
I'll keep on digging on the sdcard corruption by reboot issue.
Thanks again.
Click to expand...
Click to collapse
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
khan.orak said:
After this, the last thing on my mind is the HBOOT. You can flash original HBOOT 2.15 anew with the help of this post http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274
But if the bootloops persist even after trying all of this, maybe the car charger has done something to the battery or some other hardware part.
Best of luck!
Click to expand...
Click to collapse
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
sending 'zip' (400 KB)...
OKAY [ 0.226s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 1.735s
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
mortek said:
I rebooted the phone in order to flash an OTA for the Viper ROM and I went into the familiar bootloop again.
So I tried flashing the original HBOOT 2.15 using the method you pointed out and I got this reply:
...........
I then tried clearing storage with stock recovery but once again I am stuck with that bootloop. :s
Click to expand...
Click to collapse
I suspect hardware failure.
Sent from my HTC One S using Tapatalk 4 Beta
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
booenson said:
Trying to get back to stock so I can send my phone in for repairs, followed all your steps, and I'm coming from TrickDroid 10. Previously, I had the Rogers/Fido 4.1.1 OTA which brought my hboot to 2.15. I downloaded this OTA , followed all your steps exactly but when I tried flashing the OTA.zip I get the following error:
E:Error in /sdcard/OTA.zip
(Status 6)
Error flashing zip '/sdcard/OTA.zip'
Updating partition details...
Then in bold, red letter it says "Failed" near the menus.
Click to expand...
Click to collapse
What recovery did you use? And did you edit updater script using notepad++?
Edit: Yup, after searching, Error Status 6 appears when you edit the UPDATER-SCRIPT using wordpad/windows editor which messes all that is inside it. Use Notepad++
khan.orak said:
What recovery did you use? And did you edit updater script using notepad++?
Click to expand...
Click to collapse
TWRP 2.4.1.0. No, I used notepad, but after googling and reading the differences between notepad++ and notepad, I will have to re edit with notepad++. Will try again tomorrow when I have more time, I still need to use this phone for work and can't have it bricked lol
Tried this again, flash went through and then flashed the boot.img included with the OTA zip, and my phones stuck at the "htc one" loading screen
Edit: relocked, flashed the stock recovery, thought it was still stuck at the loading screen so I unlocked it then went to install TWRP again to restore my nandroid, and it decided to finally boot. I guess I just needed to give it more time, currently back on 4.1.1, time to send this thing in under warranty so I can get my 3G/HSPA+ fixed. Thanks!
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
asdfasdfvful said:
Just wondering, am I able to use an ota from another carrier to update my firmware and hboot as long as it fits my Cid? I believe my Cid is the global 001
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I think yes. You can check if you CID is supported. It is inside the OTA.zip\firmware.zip, a file named android-info.txt and the supported CIDs will be there.
Edit: You should first check your CID. Download CID GETTER from Play Store. Shows CID in red on top.
I have a rooted Nexus 5 on KTU84p and I'm following the steps outline in this thread to try to update to 5.0
I fall under Scenario 3, and went ahead an uninstalled Xposed. I then downloaded the OTA zip and tried to update it in TWRP. I've now tried multiple versions (currently v2.8.2.0, tried v2.8.1.0 and a v2.6..), however, all have failed with the following error:
TWRP:
E: Error executing updater binary in zip '/sdcard/ROMs/c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip'
I'm stuck and unsure what to do next - suggestions?
Nt sure bt ota is meant to be flashed in stock recovery not twrp
doctor_droid said:
Nt sure bt ota is meant to be flashed in stock recovery not twrp
Click to expand...
Click to collapse
The OTA thread has steps on how to flash via custom recovery, which is what I was following, so I'm assuming (hoping) that I don't need to go back to stock recovery...
shikhan said:
I have a rooted Nexus 5 on KTU84p and I'm following the steps outline in this thread to try to update to 5.0
I fall under Scenario 3, and went ahead an uninstalled Xposed. I then downloaded the OTA zip and tried to update it in TWRP. I've now tried multiple versions (currently v2.8.2.0, tried v2.8.1.0 and a v2.6..), however, all have failed with the following error:
TWRP:
E: Error executing updater binary in zip '/sdcard/ROMs/c1a33561be84a8a6a7d5a4c8e3463c4db9352ce6.signed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip'
I'm stuck and unsure what to do next - suggestions?
Click to expand...
Click to collapse
You have to have the stock recovery, kernel and system. You can flash those in fastboot using the 4.4.4 factory image. Then either take the ota from your device or sideload it in the stock recovery using adb.
Sent from my Nexus 9 using XDA Free mobile app
shikhan said:
The OTA thread has steps on how to flash via custom recovery, which is what I was following, so I'm assuming (hoping) that I don't need to go back to stock recovery...
Click to expand...
Click to collapse
Custom recoveries cant flash ota ....afaik
Thanks guys - I'll revert to the stock recovery then.
Can someone confirm that all I need to do is to do run the following adb cmd (using the stock recovery from here):
fastboot flash recovery "jjd-stock ktu84p-recovery.zip"
Or download wugfresh n5 toolkit
Sent from my Nexus 5 using XDA Free mobile app
shikhan said:
Thanks guys - I'll revert to the stock recovery then.
Can someone confirm that all I need to do is to do run the following adb cmd (using the stock recovery from here):
fastboot flash recovery "jjd-stock ktu84p-recovery.zip"
Click to expand...
Click to collapse
I believe that file is meant to be flashed via recovery, not fastboot. If you want to be 100% certain, just grab the factory image from HERE,
unzip it and flash the recovery.img with this command-
Code:
fastboot flash recovery recovery.img
You should be good to go after that.
rickballs said:
Or download wugfresh n5 toolkit
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No. Do not use or recommend toolkits.
Twrp was able to flash OTAs. If that's not the case anymore, then it's more than likely that a update to work with L is needed.
Pretty sure has something to do with the security that was implemented in android 5.0 that prevents this from custom recovery.
Hi there,
since there is an official cwm on their website I wanted to ask how to flash it.
1. There's only a N8013 package, can I flash that on my N8010, since these two are basically the same?
2. It's an img file. Do I need to flash this with fastboot or can I just rename it to recovery.img and flash it with Odin? I've looked at some Odin tar files from twrp and there's nothing in there except an recovery.img. Or has the img file to be specific for Odin?
Kamairo said:
2. It's an img file. Do I need to flash this with fastboot or can I just rename it to recovery.img and flash it with Odin? I've looked at some Odin tar files from twrp and there's nothing in there except an recovery.img. Or has the img file to be specific for Odin?
Click to expand...
Click to collapse
IIRC fastboot does not work for the Note 10.1. Anything for this device should be ODIN specific.
mendacium said:
IIRC fastboot does not work for the Note 10.1. Anything for this device should be ODIN specific.
Click to expand...
Click to collapse
I definitely read a guide where the img file was pushed manually. But you might be right about fastboot, I think it was an adb command.
I still think *repacking* for Odin is just naming the file recovery.img and zipping it into a tar. Can any of the devs confirm that? I mean, I must be able to flash CWM img somehow...
Hmm...
You might be right about adb push....
I can't help you with Odin, but I have flashed img files onto my N8010 using heimdall. That is sort of the Linux and Mac alternative to Odin. It runs on Windows as well so maybe it's worth a shot.
Just stumbled across this: http://forum.xda-developers.com/showthread.php?t=2102677
All there in the manual!
mendacium said:
Hmm...
You might be right about adb push....
I can't help you with Odin, but I have flashed img files onto my N8010 using heimdall. That is sort of the Linux and Mac alternative to Odin. It runs on Windows as well so maybe it's worth a shot.
Just stumbled across this: http://forum.xda-developers.com/showthread.php?t=2102677
All there in the manual!
Click to expand...
Click to collapse
Yeah, I know that thread, but that's not the latest version. Anyways, I found a guide on how to make flashable tars. So either I try that or heimdall. Thx so far!
Sent from my Galaxy Note 10.1
I'm currently on Verizon Version :5.0.1 Software :4.17.605.5. Is there a Marshmallow Rom that I can flash that will update firmware and give me the security/stagefrieght patches that verizon put out months ago? I'm rooted and S-off.
beeper10 said:
I'm currently on Verizon Version :5.0.1 Software :4.17.605.5. Is there a Marshmallow Rom that I can flash that will update firmware and give me the security/stagefrieght patches that verizon put out months ago? I'm rooted and S-off.
Click to expand...
Click to collapse
You can run MM ROMs, yes. There is one from Santod040 that is based off HTC Sense, and one by enewman17 that is based off GPe (Google Play edition)
There is no MM firmware however, until HTC releases it to us.
You can flash the latest 4.17.605.9 LP firmware, and run those above said MM ROMs
Where would I find and how would I flash the firmware..... Through twrp?
beeper10 said:
Where would I find and how would I flash the firmware..... Through twrp?
Click to expand...
Click to collapse
Verizon m8 Development forum: LINK
Latest Verizon firmware and instructions: LINK
Marshmallow Google Play Edition for Vzw m8: LINK
Marshmallow Sense 7 for Vzw m8: LINK
I tried updating the firmware with installing the above zip and it fails.
I've tried to flash the all in one update a bunch of times and it continuously fails.
beeper10 said:
I've tried to flash the all in one update a bunch of times and it continuously fails.
Click to expand...
Click to collapse
Need more info then "it fails".
Exact error or issue you encounter.
Pasting the terminal input and output here would be most useful.
Hard to instruct you any further from what little info you gave.
I'm doing it from the phone and there's no way I can copy and paste the results..... I tried to take a screen shot but that wouldn't work either. It doesn't give a reason it just goes to install and fails. Not sure how to give more info?
Here's a couple pictures of the issue.
beeper10 said:
Here's a couple pictures of the issue.
Click to expand...
Click to collapse
You don't flash it in recovery...
It fails because you aren't following the instructions given...
Copied from Santods thread:
http://forum.xda-developers.com/showpost.php?p=62734094&postcount=2
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip to make it simple/optional)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
I left my computer at work... Is there anyway to do it from the phone?
beeper10 said:
I left my computer at work... Is there anyway to do it from the phone?
Click to expand...
Click to collapse
Yes... By using an sdcard...
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once furmware is detected by phone.
That I have! That's were I was trying to flash it from.
beeper10 said:
That I have! That's were I was trying to flash it from.
Click to expand...
Click to collapse
Again.... You do NOT flash in recovery.
And I'll post again...
Please follow the instructions.
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once firmware is detected by phone.