Hi all,
On monday I was looking forward to download Froyo, and since then I live a nightmare. Everything starts cool, it downloaded, it installed itself, and when it restarted.... NIGHTMARE, it started to keep on restarting every two o three minutes after saying the system has a problem.
Since that moment I lost Wifi and mobile features, as well as SD-card reading posibilities.
What I found after some reboots is that I could get into the bootloader and select Recovery, and so I did... and I chose wipe data/factory reset. Everything got delete, and now I could see the screen when it loads (HTC Sense screen).
After this I have tried almost everything, a goldcard to copy a new update.zip file (but when I do it I got the following message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
And this had happen with any single update.zip file I found in these forums and others.
I have tried to use revoked3, and I got an error saying it can not keep on installed.
So... do i have a brick or does someone know how to fix this problem?
Thank you very much in advance for any piece of help.
Guillermo
did you update to the latest radio ?
hittori said:
After this I have tried almost everything, a goldcard to copy a new update.zip file (but when I do it I got the following message:
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
And this had happen with any single update.zip file I found in these forums and others.
I have tried to use revoked3, and I got an error saying it can not keep on installed.
Click to expand...
Click to collapse
I haven't used revoked recovery, but I know that ROM Manager recovery has an option to 'disable signature verification' (or similar wording) that should get rid of your verify option. As for the reboot loop, usually if you remove the SD card completely, and go into fastboot mode and wipe storage, you get booted up ok.
In my experience, its pretty near impossible to permanently brick an Android handset, so keep at it. You will get it working fully again in the end.
(I lost SD, BT and USB functionality in late July and had everything working again in 24 hours - after lots of panic and stress!).
Feel free to PM me if you get totally stuck.
When and how??
I think I did not, but I did not know I have to do it. I mean, my phone was working fine, I download FROYO, it crashs.... when should I put a new Radio????
Best regards
Solution at last
Thanks to dez_bordes, we found out that I have to use r6 method and it does works.
Thank you very much indeed.
Guillermo.
Welcome. hope you help me a job
I have HTC's Desire ROOT
The state of the machine is still up normally and works fine, but Andoid not get the memory card, no recovery
As children learn to bring the phenomenon known as USB-Brick, Brick SDCard. and on the forums have dealt with software Address. Today I read of your experience you should want to help
because no good at computer should not know
wish you a detailed step by step guide 1 is not?
bban hope this helps for me. tks you more
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
Hello experienced gurus out there, I am in need of some help tonight.
Here is my scenario:
I started out tonight with a stock rooted INC. I saw the thread for the new Skyraider and thought I would try and install it. I went ahead and pushed the PB31IMG to unroot and go back to bare bones stock. I rebooted and then installed Verizon's OTA as instructed in the thread on how to upgrade the radio. I then removed the PB31IMG from my SD card and installed the Dinc_OTA file to upgrade the radio. That went through fine and I double-checked to make sure the baseband version was correct which it was. Next, I rooted using UNrevoked 3 and then make a Nand backup immediately after. I rebooted the phone and then set up my Google account and downloaded Rom Manager from the Market. I flashed the ClockworkMod from ROM manager and then proceeded to Install ROM from SD card option. It goes into recovery and I see a screen with a red exclamation point and the little Android guy and then I hit vol up + Power to go to the recovery menu. I selected install zip from SD and then selected the Skyraider zip and confirmed installation.
It started going through files and in the end gives me a message that says "Installation aborted"
Here is what it actually says on the screen in its entirety (in case this helps):
ClockworkMod Recovery v2.5.0.1
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
--Installing: SDCARD:SkyRaider2.2Vanilla.zip
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
Thats it...
The first time I tried this, instead of hitting install from SD, I rebooted it to check the system version and then went to ROM manager again. Aas soon as it started it came up with this message that gave three options it seemed. One said "broken" recovery" and I forget what the other said, but it gave a link to email the developer Koush.. something. I clicked where it said broken recovery and then tried installing ROM from SD again in ROM manager. It brought me to the Recovery screen and thats when I went into the Recovery Menu and tried pushing the file from there and then got the installation aborted message that I typed out up there^^^
What should I do? Try to re-install ClockworkMod? Revert back to the old radio and then start from scratch? Anybody in the know please help me.
I reflashed Unrevoked and now SkyRaider IS installing. Just a glitch I guess, although I DID have Superuser before.
Now, I was using 5.2 flashed over 5.1.11, now I decided to do clean installation(after wiping).
I did full_wipe_1.5_ext4--->then used format_data_to_ext4 from the first post in this thread--->get error when I tried to install 5.2(the md5 is ok, I installed it from this zip).
Then I tried again to full_wipe...and I get error in it--->then I tried full_wipe 1.3(worked)--->format_data_to_ext4(worked without error)---->but when I tried to install the rom(5.2) I got "formatting partition proccess--->e: error in /sdcard/android_rev....5.2.zip (status 1)
So, I am without any rom, can't install... I guess I ****ed it up when I applied format_data when I started. Now I will be thankful if someone join realtime to help me, I guess it's got something to do with mount/unmount but I don't know what exactly to m/un, and I don't want to **** it up more. Someone for steps on repairing this and install clean 5.2?
For deleting. The problem emerge because I needed to manually unmount /cache... strange.
Just purchased the P8000 with the stock UI and all those little apps they install that no one ever actually wants.
Is there a rom I can install that will basically put this back to being what I think is a standard UK phone. It versions are presently as follows.
Android V 5.1
BaseBand V: MOLY.LR9.W1444.MD.LWTGLMP.V16.P10
Kernel: 3.10.65
Build No: ALPS.L1.MP3.V2.NB6753.65U.L1_P22
Custom Build Version: Elephone_P9000_20151014
thanks in advance
You should try Eragon rom, this is much better than stock although it is based on stock it has been improved greatly. This is the only fully working rom at present.
http://forum.xda-developers.com/elephone-p8000/development/rom-06-9-eragon-1-0-android-5-1-t3195007
Sorry thats not true, there is a vibe and flyme rom but they either have Chinese apps or lots of features we can use.
Thats the one I think I am going to look at this evening when I get home, thanks. Cant understand why they have some great and cheap phones coming out of Asia but insist on filling them up with bloatware...
Personally I dont think the p8000 has much bloat especially compared to samsung phones. I am sure you will enjoy Eragon.
I lost my phone (lenovo) in Dubai, was not handed in at the airport, no surprises there, so this is a cheap alternative.
Anyway, followed the instructions, and my screen looks nothing like the one on the Elephone instructions page.
I can see the recovery function, but when I select it, the Elephone logo appears for a few seconds, then I have a dead Android icon, with red triangle and exclamation mark, so I cant even root the thing yet, even following their instructions
Try using philz recovery, this is what I use. Its a scatter file just like elephones clockworkmod version. Just to confirm, are you holding volume up button and power at the same time which brings up the bootloader. Then select what you want with volume up and confirm with volume down?
http://forum.xda-developers.com/ele...covery-philz-touch-6-59-0-port-p8000-t3224478
ok Im going to have another go at this, as I am not sure I did anything right.
Looking at the Phillz Link, it takes me to the flash info at Elephones site.
Followed the instructions and selected scatter file, flashtool download took about 4 seconds, max.
Came up with the big green tick in the window
Now is where I am lost, because it says the rom download is now completed, but nothing on the phone has changed, and there appear to be no more instructions?
What exactly have I just done, because its not entirely clear.
I am assuming I just downloaded a backup copy of the rom I have presently installed, the stock P8000 rom, but the instructions are not exactly clear on this
ok, this time on holding power and vol down I got a different display, but sadly the 4 available options were in chinese so I have no idea which one to select, and I suspect the next page, should I guess right, will also be in Chinese, so I guess I cant do this,
Right, making some, little, progress.
Now get into bootloader (instructions are not quite right for me, have to do Pwr + Vol Down, then select recovery, then hold power and vol up to get into bootloader
Anyway, select eragon from folders, and it starts then says failed with an error aborted.
Back to try again, with new fresh download
ok following the instructions from Eragon, I get to the select the zip and it starts and fails, however, I place the zip fileon what I know is the external microSD I put in the phone, but I get the feeling that during the start process it un-mounts this drive and thus fails immediately.
So, I am now able to do as follows.
Put ZIP onto external SD
Boot into Bootloader
factory reset phone
Select ZIP
Start install
fail with following information
E:cannot mount custom path
E:you must first setup a valid folder
/storage/sdcard1: Checking
/storage/sdcard1: mounted
Calculating MD5sum....
I then select YES - INSTALL Eragon_P8000_V_5.5.0.zip
Installing:/storage/sdcard1/Eragon_P8000_V_5.5.0.zip
Finding update package...
Opening update package...
E:/Cant Open storage/sdcard1/Eragon_P8000_V_5.5.0.zip
(bad)
E:Installation aborted
Press any key to continue
lovely, looks like its bricked.
Get logo nothing else
Can get to the android menu where it says recovery, something I cant read and normal, but recovery does nothing
Which revovery do you use?
Use thePhillz Touch recovery, cwm have problems with external sd.
Best way to install it is for you via SPFlash tool.
If you done with that, you can boot into bootloader and choose there recovery.
Than you should be able to install the marvelous Eragon ROM.
hth
Cheers
sorry Im not following you.
I have the flash tool software
I appear to no longer be able to get into the bootloader.
can I upgrade the firmware to Eragon using the flashtool?
I have to say, I am a very technical person but this is a baffling process.
I am well versed in rom updates on MB, Tablets etc, all of which should be similar.
after trying both the Eragon and Phillz instructions, nether worked for me
Then I found the phone sat at the logo and I was unable to do anything
Now, for unknown reasons it let me into the bootloader again
I am now able to factory reset
I am not going to try Eragon because it simply will not let me do it
Are you all sure you have the same phone, or that there are not perhaps some versions of the same phone where these instructions are not right?
What seems simple to do is proving impossible to do
Why else able to enter the recovery
111
spottedhaggis said:
I have to say, I am a very technical person but this is a baffling process.
I am well versed in rom updates on MB, Tablets etc, all of which should be similar.
after trying both the Eragon and Phillz instructions, nether worked for me
Then I found the phone sat at the logo and I was unable to do anything
Now, for unknown reasons it let me into the bootloader again
I am now able to factory reset
I am not going to try Eragon because it simply will not let me do it
Are you all sure you have the same phone, or that there are not perhaps some versions of the same phone where these instructions are not right?
What seems simple to do is proving impossible to do
Click to expand...
Click to collapse
I had trouble getting Philz recovery to load to phone but finally got it to work using the latest version of SP flash tool from Android MTK. Google to find it. Load the scatter.txt from unzipped Philz recovery, click download, attach powered off phone to PC. Only took a few minutes to load for me.
spottedhaggis said:
ok following the instructions from Eragon, I get to the select the zip and it starts and fails, however, I place the zip fileon what I know is the external microSD I put in the phone, but I get the feeling that during the start process it un-mounts this drive and thus fails immediately.
So, I am now able to do as follows.
Put ZIP onto external SD
Boot into Bootloader
factory reset phone
Select ZIP
Start install
fail with following information
E:cannot mount custom path
E:you must first setup a valid folder
/storage/sdcard1: Checking
/storage/sdcard1: mounted
Calculating MD5sum....
I then select YES - INSTALL Eragon_P8000_V_5.5.0.zip
Installing:/storage/sdcard1/Eragon_P8000_V_5.5.0.zip
Finding update package...
Opening update package...
E:/Cant Open storage/sdcard1/Eragon_P8000_V_5.5.0.zip
(bad)
E:Installation aborted
Press any key to continue
Click to expand...
Click to collapse
you still have the problem? if yes send me a pm . i can help
Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.
dkmoore said:
Hello,
I have the following situation. A friend attempted an Android 13 sideload update on a Nokia G10 (TA-1334) using the package provided here: https://www.theupdatebox.com/nokia-g10-and-nokia-g20-get-android-13-update-download/ .
Unfortunately he didn't backup the phone first and as far as he told me he neither had Google sync turned on. The update failed.
Now the phone doesn't boot anymore and displays the standard message: Your device is corrupt. It can't be trusted and may not work properly.
I managed to enter recovery mode and retried the same sideload update, with the same package. The update seems to progress ok up to verifying the package, but after fails with the same result. The detailed log displayed on the phone screen is:
Supported API: 3
Finding update package...
Verifying update package...
Update package verification took 216.6 s (result 0).
Installing update...
E: Package is for product ROGA|ROGA_sprout but expected ROGA_sprout
I don't have much experience with ADB, sideload updates and Android in general, but since the verification looks like passing and the failure is immediately after, my assumption is that this is simply a string mismatch with the package metadata. There is this field in the metadata file "pre-device=ROGA|ROGA_sprout", which I assume it indicates that the update fits for both types of devices ROGA and ROGA_sprout but I guess this is not interpreted correctly. I removed the "ROGA" part and left only "ROGA_sprout", but obviously the update then fails with a signature error.
So, my questions are:
1) Does somebody know where we could get another sideload update only for ROGA_sprout? Or maybe any way to "fix" the referenced update to pass the thrown error. It would be fine also with an older version of Android if possible to recover.
2) It looks possible to do a factory reset from the recovery mode, but as I mentioned, unfortunately nothing was backed up. In case there's no chance to find another sideload update that could install properly, is there any way to try saving something from the phone in the current state? AFAIK the factory reset wipes out everything.
Again, I don't have much experience with sideload updates for Android phones, so sorry if I got anything wrong above.
Thank you in advance for any advice.
Click to expand...
Click to collapse
You should not have done that.
Nokia does not allow sideloading on this device. Please check your PM.