Related
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
I'm having the exact same problem with a GT-i9020 so would be interested in any help on this!
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
May need to format phone. Basically reflash latest update via boot loader. Wipe system to factory. And wipe sd
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Highl1 said:
but I downloaded 2.3.6 stock from here, unpacked in the same folder where adb and fastboot are, and tried to do fastboot flash boot boot.img and so, and didn't work, was bugging me that bootloader isn't unlock
Click to expand...
Click to collapse
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
RANDYRKELLY said:
That's the problem dude u don't unpack it. U need to leave as a update zip. Look on xda for the stock 4.0.3 update zip or wait till I provide link. U go thru stock recovery if unrooted, and flash with it. To unlock boot loader u need to be in fastboot and type fastboot oem unlock. But u wait first. Lets get it booted. I'll find link.
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
I'll wait for your link and instructions, it's obvious that I am doing something wrong
Thanks mate!
RANDYRKELLY said:
Read here
http://www.androidcentral.com/how-manually-update-your-gsm-nexus-s-ice-cream-sandwich
Sent from my Full Android on Crespo using Tapatalk
Click to expand...
Click to collapse
But I have stock recovery and can't copy anything to internal memory, since my phone doesn't boot
Highl1 said:
I know there have been similar threads, and I'm sorry that I'm raising another one. But reading to all those old topics didn't help me.
It's a friend's i9020T, bought in the US, so returning it back would be a real problem. He never unlocked bootloader, never applied any custom ROMs or Recovery, always updated it over OTA, and sometime in November, after reboots, phone started to hang on Google logo. Usually, it helped to remove the battery and wait some time, but it doesn't any more. We tried to remove it for a full day, didn't helped.
I tried going into recovery and doing full wipe and cache wipe - didn't help
I tried to unlock the bootloader, can select 'Yes', apply it via Power button, but the phone hangs.
If I want to flash anything with fastboot (boot, system img), it complains about locked bootloader
I tried Odin as well, but can't trick the phone into download mode with both volume up and down, again reports to unlock the bootloader
Is there any way to and how to fix this? I cannot transfer anything to internal memory, have stock recovery?
Thanks a lot to all of those who are willing to help, and I've really want to somehow fix the phone, because I don't have here in Serbia where to repair it. Several mobile providers only imported i9023, so they can't fix i9020T
Click to expand...
Click to collapse
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
surdu_petru said:
First download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat - that will root your phone and installed new ClockWordMod Recovery
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
Click to expand...
Click to collapse
Same thing mate, I ran it, click two times in console, can't unlock the bootloader, I always get stuck on it
Trying to update the drivers for Nexus S : http://www.4shared.com/rar/_bgEMHqk/Nexus_S_Drivers_x86__x64.html
and after that try to run.bat...Good luck!
I'll try today, but my problem is that adb cannot find the device, fastboot can
I would try downloading the full OTA from this thread, rename it to update.zip (for easy typing), place it in a directory where you can run fastboot, then use the command:
Code:
fastboot update update.zip
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Is the problem solved？
szk5230 said:
Is the problem solved？
Click to expand...
Click to collapse
Not so far, I'm still having trouble with the phone, and no solution so far helped
Highl1 said:
I got an error
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Should I create android-info.txt (how?) and place it into the zip (where?)
Thanks.
<edit> I saw this topic http://forum.xda-developers.com/showthread.php?t=1131588 and followed this http://forum.xda-developers.com/showthread.php?t=884416&highlight=STOCK but that as well complains about a locked bootloader </edit>
Click to expand...
Click to collapse
Sorry my bad, haven't tried that before either...
If it bugs you the bootloader isn't unlcoked before flashing can't you just use
fastboot oem unlock
then commence with flashing your stock image?
Edit - Nevermind...I see you tried that.
any other suggestion? I'm out of ideas
I had this problem in December. I tried everything you tried without any luck so eventually took it back for warranty repair. Unfortunately I had some water damage from 9 months before so they wouldn't touch it. Luckily I got it replaced on my phone insurance but they said it couldn't repaired.
As far as I know it's a hardware fault. With CWM it looked like I could transfer files into the sd but they would disappear! I was able to use Fastboot and Odin but no joy. I had the same errors when trying to apply update using fastboot and never found answers about the "missing" files.
Sorry to come with bad news and good luck! I'm worried it'll happen to my replacement handset so keen to know if you resolve it.
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.
After flashing sense rom (walkman sense) pico freezes and automatically restarting.. :crying:
Tried flashing super_wipe.zip before flashing rom, and tried other roms too (cm11,carbon,nextgen,jaggy..!! ). The problem still persist..
How to fix this..??
Pee_kee said:
After flashing sense rom (walkman sense) pico freezes and automatically restarting.. :crying:
Tried flashing super_wipe.zip before flashing rom, and tried other roms too (cm11,carbon,nextgen,jaggy..!! ). The problem still persist..
How to fix this..??
Click to expand...
Click to collapse
some questions/ info needed
What recovery you using at the moment
Did you format everything but sdcard
Which firmware are you on / which region
anonymous-user said:
some questions/ info needed
What recovery you using at the moment
Did you format everything but sdcard
Which firmware are you on / which region
Click to expand...
Click to collapse
recovery : Latest TWRP
formatted every thing.. flashed superwipe.zip
am in india using Walkman sense rom 5.10.
problem persist in all rom..
Pee_kee said:
recovery : Latest TWRP
formatted every thing.. flashed superwipe.zip
am in india using Walkman sense rom 5.10.
problem persist in all rom..
Click to expand...
Click to collapse
ok, well have you tried relocking your bootloader and flashing RUU package back to full clean stock? if you`ve already done that properly (not by flashing some custom stock rom through recovery) then I guess its a repair shop job.
anonymous-user said:
ok, well have you tried relocking your bootloader and flashing RUU package back to full clean stock? if you`ve already done that properly (not by flashing some custom stock rom through recovery) then I guess its a repair shop job.
Click to expand...
Click to collapse
I didn't do that /*relocking your bootloader and flashing RUU package*/..
well, let me seek tutorials to do that.
Any tutorial with less risk than this one.? http://forum.xda-developers.com/showthread.php?t=1500165
Pee_kee said:
Any tutorial with less risk than this one.? http://forum.xda-developers.com/showthread.php?t=1500165
Click to expand...
Click to collapse
1st you need to find your firmware version, boot into bootloader and the info is there and then download the appropriate RUU package as these are region specific, I can tell you how to do it without much hassle so long as you have adb setup on your comp already and the unlock token or application used to unlock your bootloader.......
you can find all the RUU packages for pico here : http://www.androidruu.com/?developer=Pico
tell me which 1 it is and I`ll extract the files needed to be able to update it via sdcard
anonymous-user said:
1st you need to find your firmware version, boot into bootloader and the info is there and then download the appropriate RUU package as these are region specific, I can tell you how to do it without much hassle so long as you have adb setup on your comp already and the unlock token or application used to unlock your bootloader.......
you can find all the RUU packages for pico here : http://www.androidruu.com/?developer=Pico
tell me which 1 it is and I`ll extract the files needed to be able to update it via sdcard
Click to expand...
Click to collapse
This is RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80.09H_1.11.82.17_release_230683_signed.exe
Pee_kee said:
This is RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80.09H_1.11.82.17_release_230683_signed.exe
Click to expand...
Click to collapse
ok I have the specific RUU package for your region downloaded and I`ve extracted the rom.zip from the package, now I`m in the process of uploading the file for you. So you have adb working? the unlock token you used to unlock your bootloader or utility that will do the same job?
Ok here`s the full procedure for you
Download the the full firmware stock rom from here: http://www.freefilehosting.net/pj03img press "DOWNLAD THIS FILE" then enter the captcha, the file name is "PJ03IMG" do not modify it in anyway.
Copy the PJ03IMG file to the root of your sdcard (not in any folder)
Boot to Bootloader and connect usb to phone and computer, open CMD on windows or Terminal on Linux and type the following:
Code:
fastboot oem lock
you should now see on the phone that your bootloader has been "re-locked" if you see that you can now press the power button on phone to change to bootloader (mode see attached pic 1 at the bottom), now the phone will look for files on your sdcard (see pic 2 attached at the bottom)
at this point it should find the PJ03IMG file and a loading bar will appear on the right hand side, be patient it takes about 30 secs to load it. When its finished it will ask if you want to flash the update or not, use the volume keys to move the selector to yes and press the power button and the process will begin to totally reflash your phone back to stock once done it will ask you to reboot phone, voila done. the first boot will take some time as its a fresh install so give it afew minutes to get to homescreen, assuming all is well and phone is working as it should we can get a recovery back after unlocking the bootloader.
anonymous-user said:
will ask if you want to flash the update or not, use the volume keys to move the selector to yes and press the power button and the process will begin to totally reflash your phone back to stock
Click to expand...
Click to collapse
how pico do that without stock rom file.?! Where i should should keep rom.zip file.? how can i extract it from RUU_Pico_hTC_Asia_India_1.31.720.3_Radio_10.35d.80 .09H_1.11.82.17_release_230683_signed.exe..??
Hi guys,
My phone now is on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
What are the steps to return the htc u11 to stock please?
The original software number of my phone is: 1.11.400.4
EDIT: I went to: https://forum.xda-developers.com/showpost.php?p=72425224&postcount=5
& downloaded stock recovery & nandroid TWRP backup (for 1.11.400.4).
However, I couldnt flash that nandroid TWRP from TWRP recovery.
Long story short, I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
dsymbol said:
Hi guys,
What's the process of returning the htc u11 to stock please?
Googling doesn't give me much result.
Long story short but I just got the phone today, I made a big mistake by not inserting the simcard in & testing to see if the phone working or not.
So, I went straight through the process of unlocking bootloader, installing TWRP, Rooting, Installing custom ROM without making a nandroid backup.
For all that, the phone did not recognize the sim cards (tried both my sim & my gf's sim. not working)
The store will take back the phone as long as I return it to stock.
Thanks for your help!!!
Click to expand...
Click to collapse
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
purple patch said:
You'll need to download the stock rom for your verison (ruu). Hopefully one is available. Check the guide section here.
Click to expand...
Click to collapse
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
dsymbol said:
I've downloaded stock recovery & nandroid TWRP backup of my stock ROM now.
What are the steps to revert the phone to stock please?
Thanks
Click to expand...
Click to collapse
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik. I'm more of a trial and error guy lol. Read guide pages to know for certain, check HTC 10 guides, same steps.
purple patch said:
Restore the TWRP backup, check everything is working, then flash stock recovery if you need to. The stock Nandroid should include recovery asfaik.
Click to expand...
Click to collapse
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
dsymbol said:
ok so I downloaded TWRP_Backup_Untouched_System_Image_+_Boot_1.11.400.4_OCEAN_DUGL_with_recovery.
1. Transfering the TWRP backup to the phone's storage
2. Flashing that backup just like flashing the custom ROM (it says Invalid zip file format. Error ect...) Please help
3. Flashing the recovery just like flashing the TWRP using adb commands
4. Lock the bootloader? I don't know how to do this.
Please advice
Thanks purple patch
Click to expand...
Click to collapse
Get the one from here and follow instructions. That's what the thread is for. https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048. Sorry i don't have time to do the leg work for you (i'm out atm), but it's all there.
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Use the ruu, you might need the HTC drivers but in the future never not make a backup, 15 mins could save u a major headache
AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
I'm downloading it now & will report back very soon.
Thanks for the tip AllGamer!!!
AllGamer said:
download this Official RRU firmware and install it https://forum.xda-developers.com/u11/how-to/unlocked-htc-u11-software-update-6-19-t3624814
Click to expand...
Click to collapse
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
If you don't have an external SD.
1. Lock your bootloader.
2. Boot to download mode.
3. Open a cmd window and run the below commands.
fastboot orm rebootRUU (hit enter)
fastboot flash zip (drag the zip into the cmd window then hit enter)
dsymbol said:
Finished downloading & now I got an ERROR installation, something like a wrong ROM, probably because I'm currently on LeeDroid custom ROM (Build 1.03.401.6.9_g CL923215)
Please advice
Thank you
Click to expand...
Click to collapse
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
AllGamer said:
On the PC side, what was the exact error message?
you can ignore the warning from the phone side.
I had a similar issue the other day, but then I was able to run the RUU upgrade to rest my phone back to stock as I had to ship it back for a refund, to get the new Red ones
When I ran the RUU thing it wouldn't detect the phone, did a few things, and then it was finally able to detect the phone.
and when it started updating the Boot image it hung for a long while, I had to restart the phone back into download mode, then run the RUU again, and it was able to continue from there.
Click to expand...
Click to collapse
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
LeeDroid said:
Your going to need a full signed RUU zip matching your original firmware and CID buddy.
Based on your original build number its an Indian dual SIM device so here is the ruu:
https://www.androidfilehost.com/?fid=817550096634780026
1. Rename it to 2PZCIMG.zip
2. Lock your bootloader
3. Drop the zip on your external SD card.
3. Boot to download mode, at that point you will be prompted to flash... Accept... Profit.
Click to expand...
Click to collapse
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
dsymbol said:
I'm on it now & will report back!
Thank you Sir for joining the party. I have hope now
Click to expand...
Click to collapse
Added an extra step incase you don't have an external sd
dsymbol said:
It says: ERROR [130]: MODEL ID ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
The previous screen says:
Verifying that you want to update
Image version 1.03.401.6
to
Image version 1.11.617.4
Click to expand...
Click to collapse
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
michaelbsheldon said:
The 1.03.401.6 may be European software. You will need the RUU for your exact phone model from: http://www.htc.com/us/support/updates.aspx
or https://forum.xda-developers.com/u1...u-firmware-t3612048/post72425227#post72425227
Click to expand...
Click to collapse
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
LeeDroid said:
I have linked the correct ruu in my post above as per the original firmware mentioned in the op
The correct build is 1.11.400.4
Click to expand...
Click to collapse
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
dsymbol said:
I have the ext. sdcard ready.
I have a question about locking the bootloader please
To lock the bootloader, I have to do this? (found instruction from google)
adb reboot bootloader
& type in 1 of these commands & stop there if it works?
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Please advice
Click to expand...
Click to collapse
adb reboot download
fastboot oem lock
LeeDroid said:
adb reboot download
fastboot oem lock
Click to expand...
Click to collapse
Confirmation number: 5G354245BV234401U
If you have some problem with your phone like me (Settings app fc always) you can download your RUU.zip and flash it.
If your bootloader unloced no problem no need to relock.
Go to download mode and type:
Code:
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
Code:
htc_fastboot flash zip Rom.zip
This takes a couple minutes and you will most likely get a error (pre-hboot update: please flush immediately) and maybe your phone reboot sometimes.
Make sure device is still in ruu mode(black HTC screen).
Let it run and it should finish this time
After completed :
Code:
fastboot reboot
It will reboot to a fully stock build.
Just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
The most common error is typically :
FAILED (remote: 90 hboot pre-update! please flush image again immediately )
Enjoy your stock phone again.
RUU.zip links:
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_Europe_1.10.401.23_Radio_8998-002772-1711021849_release_516987_signed_2_4.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.05.709.12_Radio_8998-002772C-1710231751_release_515062_signed_2_4.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.10.709.23_Radio_8998-002772-1711021849_release_516988_signed_2_4.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.23.709.3_Radio_8998-002772-1711161638_release_518568_signed_2_4_2.zip
2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_India_SEA_1.10.400.23_Radio_8998-002772-1711021849_release_517155_signed_2_4_2.zip
If link is dead you can searc here: 2Q4DIMG
Yes i tried and worked every time for me!
You can't make a downgrade with out S-OFF!!!
(I'm not using HTC anymore but this process still working)
HTC Fastboot in 2nd post. You only need paste to fastboot and adb folder.
If you want to decrypt RUU you can use : HTC RUU Decrypt tool . You will got a system.img, boot.img, recovery.img etc...
HTC Fastboot exe : https://androidfilehost.com/?fid=95916177934550031
Thank you. I was wondering how to flashing the zips.
Thanks OP.
I want to extract the stock boot and recovery from RUU but it appears the format of RUU provided here is different from the others.
Is it still possible to extract them?
And could this RUU rename to 2Q4DIMG.zip and place to sdcard and flash from device with download mode?
bnwg said:
Thanks OP.
I want to extract the stock boot and recovery from RUU but it appears the format of RUU provided here is different from the others.
Is it still possible to extract them?
And could this RUU rename to 2Q4DIMG.zip and place to sdcard and flash from device with download mode?
Click to expand...
Click to collapse
If y want to decrypt the RUU y need this : HTC RUU Decrypt tool
You can decrypt the ruu file and y can find the system.img, boot.img, recovery.img.
I think you can place to sdcard but i didn't try this.
czifraj2 said:
If y want to decrypt the RUU y need this : HTC RUU Decrypt tool
You can decrypt the ruu file and y can find the system.img, boot.img, recovery.img.
I think you can but i didn't try this.
Click to expand...
Click to collapse
I tried this tool but it is very complicated 1
czifraj2 said:
If y want to decrypt the RUU y need this : HTC RUU Decrypt tool
You can decrypt the ruu file and y can find the system.img, boot.img, recovery.img.
I think you can but i didn't try this.
Click to expand...
Click to collapse
Yes. Confirmed it can be decrypted by the tool. Thanks.
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
hi, did you get the problem said file corrupt?
of if you have the zip, could you please upload it for me?
thank you.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
yayyyy!! finally!! it works now! thank you so much! I did tried thousands of method but this one made my phone alive again! :laugh::good:
dazehaze said:
hi, did you get the problem said file corrupt?
of if you have the zip, could you please upload it for me?
thank you.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
yayyyy!! finally!! it works now! thank you so much! I did tried thousands of method but this one made my phone alive again! :laugh::good:
Click to expand...
Click to collapse
:good::good::good::good::good:
Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
Yes i know no need to unlock bootloader but i tried root my phone
Would this allow ota again after getting red triangle error?
Thanks
Sent from my SM-N950F using Tapatalk
Eddiejam72 said:
Hi, I flashed the firmware from the microsd (fimware 1.10.400.23). As with htc 11 normal model, just rename the firmware file corresponding to the phone model in 2Q4DIMG.zip, put it in the sd card, start htc u11 plus in download mode and it's done. There is no need to have unlocked bootloader.
Click to expand...
Click to collapse
I tried to downgrade from 1.24.401.2 to 1.10.401.23 with the SD-card method (non root) because of wakelocks and the low percentage of Deep Sleep of screen time off (confirmed today by HTC Nordic today and that HTC are working on a new update. The support person didn't know any ETA).
Everything seems okay underway when flashing but after boot and finishing the setup procedure, Wifi, Google account etc. I'm still on 1.24.401.2. I used the 1.10.401.23 in the first post.
Have anyone else tried to downgrade with non root?
fasst said:
I tried to downgrade from 1.24.401.2 to 1.10.401.23 with the SD-card method (non root) because of wakelocks and the low percentage of Deep Sleep of screen time off (confirmed today by HTC Nordic today and that HTC are working on a new update. The support person didn't know any ETA).
Everything seems okay underway when flashing but after boot and finishing the setup procedure, Wifi, Google account etc. I'm still on 1.24.401.2. I used the 1.10.401.23 in the first post.
Have anyone else tried to downgrade with non root?
Click to expand...
Click to collapse
My HK model got an update today to 1.24.400.03 and devcheck is reporting 61% deep sleep.
I have had almost none since the update from 1.10 to 1.24.400.01. the .03 update seems to have solved this.
Sent from my HTC U11 plus using Tapatalk
RUU decrypt tool
dazehaze said:
I tried this tool but it is very complicated 1
Click to expand...
Click to collapse
Have a look here
This is just a FYI
fasst said:
I tried to downgrade from 1.24.401.2 to 1.10.401.23 with the SD-card method (non root) because of wakelocks and the low percentage of Deep Sleep of screen time off (confirmed today by HTC Nordic today and that HTC are working on a new update. The support person didn't know any ETA).
Everything seems okay underway when flashing but after boot and finishing the setup procedure, Wifi, Google account etc. I'm still on 1.24.401.2. I used the 1.10.401.23 in the first post.
Have anyone else tried to downgrade with non root?
Click to expand...
Click to collapse
Downgrade has nothing to do with root. You have to be S-off.
I have problem when trying to flash firmware in fastboot when I get to htc_ fastboot flash zip in terminal it's doesn't recognize order but when I try without htc_ only fastboot get error file to big, I'm using Mac!
dane1312 said:
I have problem when trying to flash firmware in fastboot when I get to htc_ fastboot flash zip in terminal it's doesn't recognize order but when I try without htc_ only fastboot get error file to big, I'm using Mac!
Click to expand...
Click to collapse
You are in oemRUU?
czifraj2 said:
You are in oemRUU?
Click to expand...
Click to collapse
Yes
I'll appreciate if you could share the HTC Arabic (HTC__J15) RUU .