Related
I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw
did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.
@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com
Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.
Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...
Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse
Yes your just not rooted anymore. Run whatever process worked for you the first time
Try whitslack's method.
EDIT: Nevermind, no can do.
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first
Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse
latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse
I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse
Hi there,
I searched for quite some time, but couldn't really find something which would help...
I used an XTC Clip to S-Off my Wildfire. After that I flashed from shipped roms a pre-2.2 rom (the first I tried didn't recognize the touch screen??). After successful RUUing and available touch screen I went on with unrevoked (latest version). The phone rebooted and unrevoked (on OS X) waits for the bootloader. The phone goes into hboot, but I can't use power or volume keys to select "recovery", so the phone comes up with 2 menu items "Action for Diag Mode" and "Press Power to Flash". I tried now a few roms (all 2.1) from shipped roms, but all with the same result. If I unplug USB, pull out battery, bring it back in and power on the phone it boots normally. I just can't do anything in hboot...
Does this rings a bell for somebody?
Many thanks in advance
best regards
meikelrix
I did the same with my wildfire and found you have to use unrevoked 3.2 to root it. You may have to go through the downgrade procedure again and then use unrevoked 3.2. It will hang after the rebooting into recovery step but by then the phone is rooted. Just close unrevoked and select reboot now on the phone
Sent from my Nexus S using XDA Premium App
Hi mvjh01,
tried that, but no luck. Still the prob of non reaction volume keys and power button. I noticed, that it "jumps to diag mode", which gives the the 2 choices...
meikelrix
meikelrix said:
Hi mvjh01,
tried that, but no luck. Still the prob of non reaction volume keys and power button. I noticed, that it "jumps to diag mode", which gives the the 2 choices...
meikelrix
Click to expand...
Click to collapse
I too noticed that problem once. Just press power off button it'll flash the ROM the that problem is solved. In your case it may have caused this problem because u might have interpertted the xtc clip in between while the it was updating ur phone.
Hi Lucky,
you mean by "press power off button" once you're in Diag, right? This just reflashes the ROM, but didn't solve the problem with the non reacting power / volume keys in hboot menu itself. Strangely enough: the power and volume keys are working in "Diag Mode"?
Its really strange.. Try to install Official RUU ROM by connecting to pc. It'll detect automatically. Try to install latest one. After that use xtc clip again to unlock it. If possible try to use xtc clip in that mode. If xtc clip doesn't work put pc49img.zip file to memory card (Gold Card) then boot it'll detect that file and it'll give instruction to install it. If that too wont work goto abd but make sure your cell is connected. Try installing update.zip using fastboot. If this too wont work then install official ROM.
For for jumbling the statement, i'm using mobile so can't explain properly.
Or flash offical 2.2 and wait for AlphaRevX which should be comming soon
After S-OFF by xtc clip, u wont get back to S-ON even on flashing froyo RUU. I didn't get u clearly what the problem is. Are u able to access hboot menu...? If yes, then it is OK.
If u can flash a froyo RUU, then better do it. Once again u will be on stock froyo with S-OFF. Now just install custom recovery through PC49IMG process. Then u can install any custom rom from the custom recovery. If u still want to use that stock rom , then u can use psneuter/gingerbreak to root it.
Get the file and process from here: http://forum.xda-developers.com/showpost.php?p=12188132&postcount=15
In case if u r unable to flash froyo RUU, and can access hboot menu, then u can update the things from hboot menu. Flash all the official contents with same PC49IMG method. That should solve any of ur problems. Then flash custom recovery through same PC49IMG method.
Sounds like the Gold card is in and we are going to the wrong mode to reflash?
solution - remove gold card at boot , reinsert it before we go into recovery mode edit (or use a standard card)
[Solved] "Unreliable Mode" after Unrevoked
@bharatgaddameedi and @morbosity: many thanks for your hints! I'm now on CM7.0.3!
Short explanation: It turned out, that a combination of both tips and "SuperOneClickv1.7" did finally the trick.
Longer explanation: Once "Unrevoked" on OS X did it's first part and re-booted the phone, it stated, that it's waiting for the bootloader. My problem: I couldn't use Power and Volume keys, in order to select "recovery" from the boot menu. So the hint to remove SD before boot (thanks again morbosity) and put it back, once hboot is there, gave me finally the navigation keys back, which I could use later on. I noticed as well, that OS X console mentioned, that unrevoked couldn't do something with USB:
ERROR: usb_read failed with status e00002ed
ERROR: usb_write failed with status e00002ed
ERROR: usb_write failed with status e000404f
ERROR: usb_write failed with status e000404f
ERROR: usb_read failed with status e000404f
ERROR: Unable to create a plug-in (e00002be)
So I tried "SuperOneClickv1.9.5" (WinXP). In that console I got a message, that all went fine, but at the end it couldn't mount the root partition. So I went to "SuperOneClick1.7", and voila it rooted the pone.
I was still somehow stuck and even with the help of "ROM Manager" I didn't come to a result. So I followed the link from bharatgaddameedi's post (thank you again). I copied the in the thread mentioned "PC49IMG.zip" to SD's root and could finally install a working ClockModRecovery, from where I could then start the installation of CM7.
Many thanks again for your help and to the forum
Best regards
meikelrix
Hi Guys,
This is my first post and its only in desperation.
I have a HTC Desire. I upgraded to 2.3.3. After reading how unrevoked doesn't work on this, I created a Goldcard and managed (all on my own) to turn the phone to s /off.
Now Im stuck, many threads explain the process in different ways (as most of them related to pre 2.3.3). So do I load a custom rom onto the Goldcard and flash from there? Also, do I need to install a rollback program first or after?
Really sorry for starting a new thread, but you will see by my profile, Ive been at this for two days .
[Takes cover for flaming session]
im no expert, indeed i have only rooted only a few days ago. I was lucky to have a unlocked phone.
I guess to help the more expert in here is maybe if you detail what now shows on the Bootscreen, eg VOL Down + Power button.
Have you now got a custom Recovery installed, the common one is Clockwork Recovery?
I believe, that Revolutionary.io is able to handle 2.3.3... anyway it what i used to Root, and it installed CWR and from recovery i was able to point it to the ROM zip file and it all installed fine.
Now i didnt need a goldcard so i cant really say if there some additional steps involved first.
u need revolutionary to make s-off, then u can root it flashing the super user zip from the documentation, u don't need the goldcard, it will also install a custom recovery
official revolutionary site: http://revolutionary.io
official revolutionary doc: http://unrevoked.com/rootwiki/doku.php/public/revolutionary
complete guide: http://wiki.rootzwiki.com/index.php/HTC_Desire
don't worry about it, we are all here to help so let me explain some things.
A goldcard is a tool that allows you to use an unbranded RUU on a branded phone, effectively de branding it, as the RUU (Rom Update Utility) ignores the CID (Customer ID) of the device.
To flash different ROM's, you will need to flash something called "recovery", there are many versions, each arguably, or questionably better than the next. In order to flash recovery, you need to download a recovery image.
Download the above file, rename it to "recovery.img" for simplicity, and put it in your C:\
now the flashing process, there are many tools and utilities you can use, but for now, let's just use command prompt as it does not require you to install anything, just as long as you get the commands right. (you'll also need the file I attached [fastboot.exe], just unzip it into your C:\)
Ok, once you've done the steps stated above, turn your phone off. With it off, PRESS AND HOLD the RETURN/BACK key on your phone, and while still holding it, press the POWER key. This will boot you into "fastboot" mode.
Plug your phone in via USB to your PC.
Open command prompt (start menu, accessories, command prompt)
type the following:
Code:
cd\
fastboot flash recovery recovery.img
Congratulations, you have now flashed recovery. This now allows you to flash ROM's.
Put whatever ROM you would like on your SD-CARD, I recommend CyanogenMod (for No Sense) or MIUI (For something completely different) or RCMixS for Sense (sense 2.1) (all comes with preference)
To boot into recovery, boot into bootloader, (while powered off, press and hold VOLUME DOWN, and POWER), use the volume keys to navigate, and the power key to select. Navigate to RECOVERY and hit power.
When you are booted into recovery, before flashing a new rom IT IS VERY IMPORTANT TO BACK UP!!. You can do this in the "backup and restore" menu.
Once you are backed up, go to "mounts and storage" and use "format [partition]" option, to format boot, system, and userdata.
Then, go to "flash zip from sdcard", and find the ROM you have chosen, and wait for it to finish flashing.
Good luck to you
Wow guys, cant thank you enough
I actually had a small amount of brain oozing out of my ears at one point Thanks for the custom info, like I said, the tuts are excellent, but being new, they are a bit irrelevant if you half way through the process. Trust me to upgrade to an 'unrootable' system a week before I decide to root it
I will remove my flame-proofing now
Thanks again
PP
@bortak
Thats only when he have s-off...If i not wrong he have the stock 2.3.3 with no root an s-on
EDIT: nevermind..i didn't read the post properly..
Hi guys
Im getting an error on fastboot :
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
Click to expand...
Click to collapse
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
palm_pilot said:
Hi guys
Im getting an error on fastboot :
Ive tried a different version ,but that came up with the same error. I have android SDK installed in the same directory, is this interfering with it?
Thanks again
PP
Click to expand...
Click to collapse
Okay, put "fastboot.exe" in c:\android-sdk\platform-tools\
and then before issuing fastboot commands, type:
Code:
cd c:\android-sdk\platform-tools\
this *should* fix it for you
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
error: cannot load 'recovery-clockwork-2.5.0.7-bravo.img'
Click to expand...
Click to collapse
Any ideas fellas?
PP
Maybe download 'recovery-clockwork-2.5.0.7-bravo.img' and then select that from unrevoked ?
palm_pilot said:
Hi Guys,
This isnt going very well for me
Ive downloaded the .img file tried to flash it. Re-downloaded another copy (in case it was corrupt) , tried to flash that. Changed the file name back to the original (along this command text) to see if it was a recognition issue
On all occasions Im geting :
Any ideas fellas?
PP
Click to expand...
Click to collapse
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
BigMrB said:
Please tell me what code you put before getting that error - or the whole cmd from start to getting that error
Click to expand...
Click to collapse
Hi
Im using :
\cd (enter)
Then :
android-sdk\platform-tools\fastboot flash recovery recovery.img
I have revolution installed, can I flash from within this ie. loading the image to the SD and running from within the phone itself?
ATB
PP
cd C:/android-sdk/platform-tools/
fastboot flash recovery recovery.img
(providing you changed the name of your recovery to recovery.img)
i followed following steps
**********************************************
S-OFF + root with flashing method
New mothod of rooting HTC WildFire (buzz) - credits go out to androidybloidy from xda.
Full topic over to xda: Rooting HTC Wildfire (BUZZ) 2.2.1 with HBOOT 1.01.0002 !! FULL GUIDE (28/6/2011) - xda-developers (sorry for copy/paste, but i really don't have the time and i wanted to save the thread somewhere else besides xda)
S-OFFing the Device
Downgrade to HTC Froyo WWE for AlphaRevX (HBOOT 1.01.0001)
You can't s-off HBOOT 1.01.0002 !
Therefore, downgrading the HBOOT to 1.01.0001 is must for the meantime, to get an efficient S-OFF.
So, here’s a small package to help you do this.
click here.
Extract this package somewhere you can find it, like your “Desktop” for example.
Step 1: run step1.bat from the package. This will downgrade your MISC partition to allow for the RUU downgrade.
At the end, GoldCardTool will start up, to allow you to create a goldcard which you will need before starting Step 2.
How to deal with Gold-Card Tool:
1. Switch off your phone, remove your microSD card.
2. Insert the microSD card into your card reader, connect it to your computer and format the card to FAT32 file system.
3. Insert the card into your HTC Wildfire and power it on.
4. Make sure USB Debugging is enabled on your phone in Menu > Settings > Applications > Development.
5. Connect the phone to your computer via USB and set the mode to charge only.
6. Launch Gold-Card Tool on your computer and click ‘GetCID’.
7. Copy the CID code from the text box and click the link shown below that text box to open it in your browser window.
8. In the browser window, enter all the details required and submit that form.
9. You should now get an email from PSAS in a few minutes. Open it and download the ‘GoldCard.img’ attachment.
10. Now set your phone’s USB mode to Mass Storage.
11. In Gold-Card Tool, click ‘Refresh’.
12. Select your mounted SD card from the drop-down menu saying “HTC MMC:”
13. Click ‘Load Goldcard.img’ and select the file downloaded in Step 11.
14. Click ‘Patch MMC’ and your Gold Card will be created. You may exit Gold Card Tool once done.
After you've made the goldcard, and patched it, continue with step 2.
Step 2: run step2.bat from the package. This will downgrade your ROM version to HTC WWE Froyo for Wildfire (unbranded).
If you get a Customer ID error while doing this, your goldcard is not working!
Create a new goldcard and re-run step2.
AlphaRevX
* Steps:
1st You need to get to: alpharev.nl/x/beta/ to download the tool, and to get your “beta key” which you’ll get in a pop-up window in the same download page after you click the download link for (windows version).
The “beta key” is a must; the tool won’t work without it!
You’ll be asked to provide your phone “serial no.”, typically it should be something like HTXXETDXXXXX, and you can get it from:
Settings --> about phone --> phone identity.
Now, do the following:
1. Run latest version of HTC Sync on your PC and connect phone in HTC Sync mode and sync all your files. Remove HTC Sync and not the drivers.
2. Reboot phone.
3. Settings->Applications->Development->Check “USB Debugging”.
4. Run AlphaRevX and connect phone to PC in “Charge Only mode”.
5. AlphaRevX should recognize your phone and show your Device Serial number.
7. Type out the “key” in the AlphaRevX software, keeping in mind the upper and lower case letters and press enter (you can copy / paste the key).
8. AlphaRevX should start doing its job and you’ll get S-OFF in less than 90 seconds.
9. If it takes longer, just wait for the 15 minutes mark, if nothing, then reboot phone and retry.
(Some members got S-OFF after multiple tries)
Rooting the device:
Step 1 - Installing the USB drivers
Download USB drivers (here) and extract them on desktop. Turn off your wildfire and boot into HBOOT by holding the VOLUME DOWN + POWER button. Connect your phone to your PC and it will show "drivers installing" or similar there for Android device. When prompted, install the drivers by going to device manager and browsing to the folder where you extracted the drivers. Once installed, disconnect and reboot your phone normally.
Now you need to install the “Android bootloader interface”.
Connect your HTC wildfire to the PC and it will ask for drivers again, now go to device manager, click on unknown device “other devices”.
Click on update driver -> install from specific location -> No i will choose to install -> choose Android phone and click on “adb interface” -> click next -> when asked to install click on continue anyway, just install them.
Once done you will see your phone recognized as "Android bootloader interface".
Now disconnect your phone and go into:
Settings -> applications - > development - > enable USB Debugging.
Step 2 - Downgrading from Android 2.2.1 Froyo to Android 2.1 Éclair
Download the RUU rom (here) which is an original stock rom. Plug your phone into the PC and set it to "Charge through USB". Double click RUU rom .exe
Follow the on screen instructions and then let it install. Your phone will reboot into stock HTC 2.1
This will be the last time you will be seeing it though.
A little extra here by me: if you download that RUU and notice after you've completed this step your touch doesn't work, don't panic. Just get a different RUU and flash again. I can't remember if i used RUU_Buzz_hTC_Asia_India_1.25.720.1_Radio_13.45.55. 24_3.35.15.31_release_142213_signed or RUU_Buzz_hTC_Asia_WWE_1.25.707.1_Radio_13.45.55.24 _3.35.15.31_release_142190_signed
but you can find more over at Shipped ROMs
Step 3 - Gaining root using Unrevoked, get ClockworkMod and set your phone free
Download the test version of unrevoked (here). Let me repeat, DO NOT USE UNREVOKED 3.32 as it will lead to CID errors or to be precise this error
"Validation error, backup CID is missing"
This may be caused as the 3.32 does not support the HBOOT. Hence you need specific test version of Unrevoked 3.2 to do the job. Download it, save it on desktop, and run it. Now connect your phone and the rooting will start. Once done, you will have ClockworkMod recovery installed on your phone.
Reboot your phone now (using the VOLUME UP/DOWN key for navigation and clicking using TRACKBALL, the POWER button takes you back in menus). Once rebooted, you will see the “Superuser” app in your phone and.... done.
Now you can download and flash cm-7 or whatever.
*********************************************
After step 2 touch screen is dead and can't put usb debugging ON.
After rebooting my phone is receiving calls but can't attend.
my HBOOT screen showing..
-Revolutionary-
BUZZ PVT SHIP S-OFF
HBOOT-6.01.1002
MICROP-0622
TOUCH PANEL-SYN3KY_01
RADIO-3.3515.31
please help me..
Install a RUU then retry the steps for rooting.
Sent from my HTC Wildfire using XDA App
but i cant on usb debugging
you shouldnt need usb debugging for a ruu.
Try to get an update file wich you can flash in Hboot. There are ones, but i dont now where... Take a sdcard reader and put the file on it.
firstly can you still get into recovery by your bootloader? if you can then flash this.
http://download.cyanogenmod.com/get/update-cm-7.1.0.1-buzz-signed.zip
then this http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
but remember to wipe your cache, dalvick cache and factory reset the phone. (all done in recovery) if that works you should be on cyanogenmod 7 and that will hopefully fix your issue.
hello there..same problem with me but resolved, successfull CM7 nightly..
try to flash with the
RUU_Buzz_HTC_WWE_1.37.405.1_Radio_13.53.55.24H_3.3 5.19.25_release_151892_signed.exe
find it in the web, run, and then you got your touchscreen works
Go to an S-ON and Unrooted state, from this guide I made.
Then use this guide I made to start over again without touchscreen problems. Quite a few people have had touchscreen problems using the other guide.
Hello,
Woke up to my phone turned off and upon turning it on showing the Your Device is corrupt error and after 30 seconds a reboot happens automatically. I remember I had a "low disk space" alert for a few days. I think there is absolutely no free disc space. I can't access recovery as when I hold down any buttons it turns on and quickly shuts down within 1 second upon the first screen showing.
Don't know what to do. I had many important files on it as well.
Any tips would be massively appreciated.
Why are we facing this issue?
+1
Any solution for this?
My device is also facing the same issue.
Mangekyō_1 said:
Hello,
Woke up to my phone turned off and upon turning it on showing the Your Device is corrupt error and after 30 seconds a reboot happens automatically. I remember I had a "low disk space" alert for a few days. I think there is absolutely no free disc space. I can't access recovery as when I hold down any buttons it turns on and quickly shuts down within 1 second upon the first screen showing.
Don't know what to do. I had many important files on it as well.
Any tips would be massively appreciated.
Click to expand...
Click to collapse
Factory reset is the only option!!
connect your phone to pc in normal charging mode and then try booting to recovery mode (power&vol+), you should be able to boot to recovery.
you will loose all your data.
Sadly this is clearly not working. There is quite a few posts on the nokia forum relating to this and the android 10 update bricking the device. But so far there is no solution and as well as that, the recovery mode is not available.
There appears to be some opportunists on youtube that are exploiting this to profit to fix the device, but that is no real help.
So I'm also in the club of a bricked Nokia (well its my mothers phone) that has remained stock the entire time. (it's a good thing I kept my Nexus 4!)
Fryingsheep said:
Sadly this is clearly not working. There is quite a few posts on the nokia forum relating to this and the android 10 update bricking the device. But so far there is no solution and as well as that, the recovery mode is not available.
There appears to be some opportunists on youtube that are exploiting this to profit to fix the device, but that is no real help.
So I'm also in the club of a bricked Nokia (well its my mothers phone) that has remained stock the entire time. (it's a good thing I kept my Nexus 4!)
Click to expand...
Click to collapse
Try booting in fastboot .
Poweroff your phone .
Connect to pc .
Press (vol- & power) until the logo appears with a little fastboot written in left bottom.
If you are able to boot into fastboot then tell me I will give you the solution.
bx2_nero said:
Try booting in fastboot .
Poweroff your phone .
Connect to pc .
Press (vol- & power) until the logo appears with a little fastboot written in left bottom.
If you are able to boot into fastboot then tell me I will give you the solution.
Click to expand...
Click to collapse
Yeah, it's refusing to go into fastboot, just keeps going in a cycle back to the corrupt error again
Fryingsheep said:
Yeah, it's refusing to go into fastboot, just keeps going in a cycle back to the corrupt error again
Click to expand...
Click to collapse
Did you connected to pc before trying to boot into fastboot.
bx2_nero said:
Did you connected to pc before trying to boot into fastboot.
Click to expand...
Click to collapse
Yeah, thats when it goes into cycle even more so, android one screen comes up, quick flash of the corrupt error, then it starts again.
Fryingsheep said:
Yeah, thats when it goes into cycle even more so, android one screen comes up, quick flash of the corrupt error, then it starts again.
Click to expand...
Click to collapse
Join this and report your problem.
t.me/HikariCalyxFIH
Sadly it is lifeless now, believe the battery has ran out and the phone refuses to charge in this state
solution
Hello i had the same problem , i recovered my 5.1 plus this worked for me maybe it works for you too.
First download sp flash tool and firmware file i have 5.1 plus world wide version and dowload the image PDA-209B-0-00WW-B06 for x5 use the image with cn not ww.
Unzip flash tool and the image PDA-209B-0-00WW-B06.
Run sp flash tool load the scatter file from the image, then unthick the box sutinfo, systeminfo_a & cda_a and hit dowload, conect youre phone holding volume up and down until it starts download.
Wait until it finish and the green box wit ok appears. Now the phone will start and after android one logo,the robot image and no comand will show up, click power button then quick on volume up and recovery menu shows.
Now you need a micro sd card and OTA update file download the Android 10 Update (V3.11A) : ace851ea59294177f677018648d6c0614317510e.zip.
Copy the zip file on the micro sd then insert it on the phone. From the recovery menu choose update from sd card then select : ace851ea59294177f677018648d6c0614317510e.zip
The update will start wait untill recovery says succesful it will take some time be patient. After that reboot all done youre device should work. Its my first post i cant post links sorry the sistem wont let me.
piticulrau said:
Hello i had the same problem , i recovered my 5.1 plus this worked for me maybe it works for you too.
First download sp flash tool and firmware file i have 5.1 plus world wide version and dowload the image PDA-209B-0-00WW-B06 for x5 use the image with cn not ww.
Unzip flash tool and the image PDA-209B-0-00WW-B06.
Run sp flash tool load the scatter file from the image, then unthick the box sutinfo, systeminfo_a & cda_a and hit dowload, conect youre phone holding volume up and down until it starts download.
Wait until it finish and the green box wit ok appears. Now the phone will start and after android one logo,the robot image and no comand will show up, click power button then quick on volume up and recovery menu shows.
Now you need a micro sd card and OTA update file download the Android 10 Update (V3.11A) : ace851ea59294177f677018648d6c0614317510e.zip.
Copy the zip file on the micro sd then insert it on the phone. From the recovery menu choose update from sd card then select : ace851ea59294177f677018648d6c0614317510e.zip
The update will start wait untill recovery says succesful it will take some time be patient. After that reboot all done youre device should work. Its my first post i cant post links sorry the sistem wont let me.
Click to expand...
Click to collapse
You left the most important step .
Readback step in SP FlashTool.
Hey folks!
Let me share what worked for me when I solved this issue on a friend's phone.
This guide is dependent on you being able to boot into recovery mode - the screen with the green android robot laying down with a red exclamation mark on top of it.
We'll use recovery mode to sideload an OTA image to the device. Go to the Nokia OTA repository on telegram (search for Nokia OTA repository). Once there search for Nokia 5.1 plus and from the search results look for a full Android 10 OTA image with the April security patch (sorry, can't post links - should be 1.23 GB). Download that file and move it to the root directory on your SD card and then insert your SD card into your device.
Now, boot into recovery mode on your device (there's a key combination that will get you there but I'm not exactly sure what it is - try Power + Volume Up or Power + Volume Down). Once you get to the recovery mode screen, press Power and Volume Up to load the recovery menu. You'll see a bunch of options listed there - the one we're keen on is 'Install zip from SD Card'. Scroll down using the Volume Down button until you get to that option and then press the Power button to select it. You should then be able to select the zip file you downloaded earlier from your SD card. The process should then take a few minutes to complete. If all goes well, you can now reboot your device and Profit!
Good luck!
bx2_nero said:
You left the most important step .
Readback step in SP FlashTool.
Click to expand...
Click to collapse
No i did not use readback , why shoud i? I have lost half a day searching on internet about this problem and i got lucky.
piticulrau said:
No i did not use readback , why shoud i? I have lost half a day searching on internet about this problem and i got lucky.
Click to expand...
Click to collapse
Readback is the most important step when you are flashing stock rom .. it backups all the partitions in a single file which you can use to restore if something goes wrong .. many users have faced issues because they didn't do the readback process . You can check out the guide for downgrade and there is nothing to search about .. if you can access recovery/fastboot then it's very easy to restore . If you can't you will have to flash the stock rom . You can check the guide in Guides thread. You just got lucky .if something went wrong you would have end up bricked up your device bad.
bx2_nero said:
Readback is the most important step when you are flashing stock rom .. it backups all the partitions in a single file which you can use to restore if something goes wrong .. many users have faced issues because they didn't do the readback process . You can check out the guide for downgrade and there is nothing to search about .. if you can access recovery/fastboot then it's very easy to restore . If you can't you will have to flash the stock rom . You can check the guide in Guides thread. You just got lucky .if something went wrong you would have end up bricked up your device bad.
Click to expand...
Click to collapse
Ok , did not know that, ill remember next time if i have same problem. Thank you. Indeed i had no way to enter recovery menu and when trying to flash i got errors the only way i could suucesfuly flash the rom was unticking those 3 boxes , after that the phone entered in recovery but it wasnt able to start normaly it bootloped to the robot with no comand ,so i had to use update from sd because sideload didnt work.
piticulrau said:
Ok , did not know that, ill remember next time if i have same problem. Thank you. Indeed i had no way to enter recovery menu and when trying to flash i got errors the only way i could suucesfuly flash the rom was unticking those 3 boxes , after that the phone entered in recovery but it wasnt able to start normaly it bootloped to the robot with no comand ,so i had to use update from sd because sideload didnt work.
Click to expand...
Click to collapse
Its very lucky that you got it work ... Sometimes this device can be very messy.
---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------
battystutor said:
Hey folks!
Let me share what worked for me when I solved this issue on a friend's phone.
This guide is dependent on you being able to boot into recovery mode - the screen with the green android robot laying down with a red exclamation mark on top of it.
We'll use recovery mode to sideload an OTA image to the device. Go to the Nokia OTA repository on telegram (search for Nokia OTA repository). Once there search for Nokia 5.1 plus and from the search results look for a full Android 10 OTA image with the April security patch (sorry, can't post links - should be 1.23 GB). Download that file and move it to the root directory on your SD card and then insert your SD card into your device.
Now, boot into recovery mode on your device (there's a key combination that will get you there but I'm not exactly sure what it is - try Power + Volume Up or Power + Volume Down). Once you get to the recovery mode screen, press Power and Volume Up to load the recovery menu. You'll see a bunch of options listed there - the one we're keen on is 'Install zip from SD Card'. Scroll down using the Volume Down button until you get to that option and then press the Power button to select it. You should then be able to select the zip file you downloaded earlier from your SD card. The process should then take a few minutes to complete. If all goes well, you can now reboot your device and Profit!
Good luck!
Click to expand...
Click to collapse
Power + VolUp - Recovery
Power + VolDown - Fastboot