Hi Guys,
Last night for some reason i downloaded the latest official Firmware and flashed it using HTC's RUU. Since then i'm unable to locate a paid app called PicSay Pro, i can find the lite version but as i paid for the full version before i'd like to download it again!
So not being able to find it i thought i'd maybe flash a different firmware only to find the Hero will not boot into the Recovery image i flashed before! I have been using Modaco 3.0 for a while before this so had the Amon RA recovery image. When holding the back button and powering on the phone it now only displays a 3d image of a yellow '!' in a white triangle next to a phone.
So now thought i'd reflash the Recovery image but while trying to reflash the recovery image i get the following error after running the fastboot command :-
'boot.img'... FAILED (remote: not allow)
Can anyone please let me know what i need to do to fix these issues?
Any help appreciated!
Thanks
Paul
If you have flashed the 'Official' firmware from HTC - you now no longer have root access/recovery image! You will need to re-root and start again.
I do not know why this is stopping you from seeing the PicSay Pro app on the market though!?!
Cheers for that mate - but the problem ive got is i can't flash any other firmware or root as i get the errors during the ADB commands - is there another way? After a bit of looking - will the goldcard method work to downgrade?
And yes the missing Picsay Pro app is an odd one - i've reflashed the Rom just to see if there was an issue in flashing and the same occurs - still unable to locate it.
The odd thing is that other paid apps are showing, bettercut and some others i've paid for just not Picsay Pro - very odd!
Anyone else have any suggestions for either issue?
Cheers
Paul
paulrgod said:
The odd thing is that other paid apps are showing, bettercut and some others i've paid for just not Picsay Pro - very odd!
Anyone else have any suggestions for either issue?
Click to expand...
Click to collapse
Since you've already bought Picsay Pro, have you tried just looking for it in "My Downloads" rather than searching for it? Whenever I wipe my phone, I pick up all my paid apps directly from there rather than searching again.
As to your problems flashing - if you've installed the latest RUU with the "perfect SPL", you will have to downgrade before you can "upgrade" again. If it is a carrier ROM you installed, you will need to use a goldcard to do this.
Regards,
Dave
Thanks Dave - i'll try the Goldcard method to downgrade tonight.
About Pic Say pro this is still a mystery - yes i'd checked in there, the other paid apps were there but still no sign of Pic Say pro....
Related
Hi @all,
I installed the latest Jesus Freke's build of the firmware (ADP 1.1). No I have the problem that my phone shows an update message every few minutes.
If I try to get into the "System Update" configuration I get a force close.
Does anyone know how to turn this off else? I think if I let it update via the automatic updater I will get into trouble or is it safe to upgrage? (used jesus freke's firmware to set symlinks to my sdcard and install the apps there).
Would be nice if someone could help me sorting that out!
Regards,
Markus
download jf1.42 and install it the standard way..
Thanks for the tip! Just did the update as usual (following the steps described here http://android-dls.com/wiki/index.php?title=Keeping_Root).
Now my phone is looping at the boot sequence (the droid is showing over and over again).
Bricked?
TheKoelnKalk said:
Thanks for the tip! Just did the update as usual (following the steps described here http://android-dls.com/wiki/index.php?title=Keeping_Root).
Now my phone is looping at the boot sequence (the droid is showing over and over again).
Bricked?
Click to expand...
Click to collapse
did you move your apps to the SD card before you upgraded?
sure, I already did that when I installed the 1.41 a few days ago
oops...I tried to redo the upgrade and noticed that there are no test keys options...**** should have watched out for that.
would a wipe help? and if it would help where does the built in nandroid put the image?
****, just cant anything now. flash_image doesnt work in recovery mode and falling back to 1.41 or previous doesnt work also.
where does nandroid store the image?
In /sdcard/nandroid/
To all devs out there ,im been trying to root the hero for a week now ,ive tried every guide going also the gold card with 10 different sd cards with no luck.the rom what ive got is the release 2.73.405.66 rom.it has the new nboot is thats why i cant flash.is there any way i can wipe all date and software so i will have nothing on the phone and then install an earlier rom, its just an idea as im starting to lose it with this fone.i hope someone can help me or do i have to wait for the official update from htc
with this rom version you need to create a goldcard and downgrade your rom before you can install a custom rom. if you have problems with the goldcard you should be more specific.
waiting for the update doesn't seem like the best idea, because it might take some until a security flaw is found that allows to root the rom when already installed on the phone. if you have the custom recovery image you will be able to install the (pre-rooted) update short time after it was released.
You should be able to use fastboot for this issue.
Search around the forums, (also http://hero.modaco.com) and read about it.
All you need is the fasboot tool, a usb cable and the "debugging mode" switched on at ur phone...
everytime i create the gold card and try to downgrade the rom it states boot error 140.i follow the guides very indepth i get the serial number from the sdcard than i reverse the string and then replace the first two numbers or letters with 2 zeros how can you tell when the goldcard is on the sdcard.when i replace the sdcard back in sdcard reader it states that the folder is empty.im quite clued up on winmo but android is giving me a headache
wouldn't the fastboot give you the "remote: not allowed" error?
anyway, you can try:
start your phone by holding back and pushing power, you should see three skating androids. put recovery image in the folder where your fastboot.exe is, open terminal and go to that folder and type:
Code:
fastboot boot recovery-RA-hero-v1.5.3.1.img
if that works report back.
for the goldcard i can't help, never did it.
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
rednose30 said:
at last im rooted thanks for for the help .the way i did
(with the phone in normal mode)
1) Connect your Hero via usb to your pc/mac/...
2) Open Command Prompt ->
Put in the following text ->
C:\Users\Username> cd\
C:\>cd android\tools\
C:\>android\tools>adb push recovery-RA-Hero-v1.5.3.1.img /sdcard/recovery-RA-Hero-v1.5.3.1.img
C:\>android\tools>adb shell flash_image recovery /sdcard/recovery-RA-Hero-v1.5.3.1.img
3) JOB DONE!
Click to expand...
Click to collapse
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
mjames_84 said:
I guys, I seem to be having the same issue as the OP. Having tried the above it tells me that there is an error writing recovery: Permission denied. Any idea how to solve this?
Thanks!
Click to expand...
Click to collapse
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
TastyBurger said:
Getting exactly the same. Tried the goldcard method numerous times using 3 different cards and always get the bootloader 140 error. Tried the above with same errors... very frustrating!
Mine is a UK T-Mobile G2 with build number 2.73.110.26, any suggestions gratefully tried!
Edit: Finally managed to sort it. I was using "RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe" - this didnt work. Once I found and tried RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe it all clicked into place!
Thanks for all the info provided on these forums, cheers!
Click to expand...
Click to collapse
Hi
I have tried making a goldcard, and installed via. the RUU shown here.. 405.5 .. but then I tried using Flashrec to get another recovery image, it failed making the first step...
So is my phone rooted or did something go wrong ?
the phone is still unfortunately not rooted. I would've tried the fastboot method
Sent from my HTC Hero using the XDA mobile application powered by Tapatalk
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
nicknyhk said:
just curious but did anyone just try to flash the older version without bothering with the goldcard...i dun know what i did to my htc hero orange but when i was researching i was told i needed to downgrade to root. I tried to take a long shot and used htc sync and old orange ruu..and somehow it just downgraded itself.... i know it might not help but its a long shot!
Click to expand...
Click to collapse
Very similar story. I did make a goldcard but hadn't got as far as finding out how to extract the update.zip out of the RUU exe, in order to use it. I tried running the RUU to see what would happen & my Hero downgraded.
Ok something dumb happened involving a flash 10.1 file meant for evo and eris. My problem is even after removing root and doing a full recovery it is still diplaying flash 10.1. I have tried uninstalling 10.1 and i could not install the flash light 4 apk ,which i found. The only way for me to play flash content on the stock unrooted device is to reinstall the flash 10.1 apk through astro. Can someone help me get back to a stock incredibe with flash light?. It wouldn't be a big deal with froyo working great but i also suffer from the grounding issue and will be returning this device.
I hope this is the right place and i thank anyone taking the time to read this.
ps i wish i could change the title to proper spelling.
Just download the stock ruu and ruu it back before you return it. This way everything is back to factory.
P.S. To edit your title, go to edit, and advanced mode.
samwathegreat said:
Just download the stock ruu and ruu it back before you return it. This way everything is back to factory.
P.S. To edit your title, go to edit, and advanced mode.
Click to expand...
Click to collapse
by that you are directing me to follow th following link, correct?
http://androidforums.com/all-things...ideo-howto-unroot-incredible-downgrading.html
After doing this flash is still not restored properly.
For further context the issue resulted from using this.
http://forum.xda-developers.com/showthread.php?t=726271
I think you're a little confused....
Stock htc droid incredibles come with flash lite ver. 10.1.123
If you take a factory-fresh incredible out of it's brand-new box and go to whatismyflash.com it will say "flash 10.1.123" but nothing about "lite".
If you already ruu'd the phone, then it s back to factory.....i don't know what you're expecting to change?
The update you applied was actually just a hack that fools some websites into thinking you have the desktop version of flash. You should be all good.
Your phone never had flash lite 4....I'm not site where you got the idea that it did, maybe confusing it with the eris?
ultimately i guess they won't look that closely at the phone, however xepisodes.com worked on my phone out the box and now it does not work on 2.1 roms. That site now only works in froyo roms with the true beta. I was confused by the whatismyflash results as well.
Last night i tried installing Clockwork Recovery on my Tab (it's a US T-Mobile model). I got an error message in ADB, but i thought i had worked through the issues. Then i installed Rom Manager and tried to make a backup through Rom Manager. It rebooted my Tab, but it never made it to Recovery; it froze on the white T-Mobile screen. At this point, i can reboot, but it always gets stuck on the white T-Mobile screen. If i hold down volume-down and power, i get into download mode, and if i hold down both volume-up and volume-down with power i get some text (sorry, can't remember specifics b/c i'm at work w/o my Tab).
I'm not a total Android noob, but i am new to Samsung (i've had a Droid and a Droid X, and i am very familiar with SBF-ing Mototorla android devices... i assumed that Samsung devices used something similar but i guess i was wrong). I feel that since i can get into download-mode, i should be able to re-flash the stock firmware and resurrect my Tab, but i'm not familiar enough with Odin (which i gather is what i'll need to use) to know HOW to do this, let alone where to get the correct version of Odin. I have found a file on these forums: T-Mobile.zip, which i think is what i'll need to flash, but again, i don't know how to do it.
I'd appreciate if someone would take pity on me and help me through my problems!
-dave
Looks like i figured it out myself. Thanks to anyone who was contemplating a reply
-d
What was the fix?
Just out of curiosity, how did you resolve it?
As i said in my original post, i had found a T-Mobile.zip file on these forums. I originally tried using Odin to flash it to my Tab without success. Then, while scouring the web for answers, i found a blog post where someone flashed that same file to his semi-bricked Tab and it worked. The video showed the version number of Odin (1.7), which was different than the version i had tried using. Sooooo, i found v1.7 online, downloaded it, and used the PDA option to flash T-Mobile.zip to my Tab... and it WORKED!
I did have a lot of force quits of my apps after rebooting, and the guy on the blog said that if this happened, to do a factory data rest. So, success AND now i know how to flash back to stock which is even better! I hope this info is useful to others who get themselves into the situation i got myself into.
-d
impulse630 said:
As i said in my original post, i had found a T-Mobile.zip file on these forums. I originally tried using Odin to flash it to my Tab without success. ack to stock which is even better! I hope this info is useful to others who get themselves into the situation i got myself into.
-d
Click to expand...
Click to collapse
Hi impulse ..can you please point to post where is the t-mobile.zip file you are referring to...is this a complete t-mobile rom which can be flashed normally using odin ..or maybe other procedure needed ....my regards.
Here's the link to the thread: http://forum.xda-developers.com/showthread.php?t=855851
-d
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
The problem is that, I couldn't find a tested (official/unofficial) ClockworkMod recovery for use with Defy XT. I could do with installing some Chinese release of ICS for Defy XT (SBF), but, I wanted to try CM10; it appeared more fascinating. So, anyway, I thought I could use Koushik's custom recovery build script on his website (builder.clockworkmod.com). So, I did the process of obtaining the stock "recovery.img", plugging it in that script, and obtained a new custom-built CWM. The real problem which I am not able to come out of is now - After flashing it, on the next reboot, it is going into the "MBM-flash mode", and it throws out an "error 0301", and doesn't go further than that. In this mode, I gathered that it will be able to communicate to a computer (RSD lite) over USB, and so, I installed it and was able to detect the device, but I'm not able to find out, what to do next to get it back to normal working condition.
Since that error screen I see now is basically a flashing tool, I was thinking, reflashing the recovery partition with the stock "recovery.img" (have a back up) should solve the problem. But, I'm not able to find out how to do it...
If there is anyone else who has faced a similar problem and found a solution, it would be really good of you to share it. Or, if there is anyone who knows how to work with RSD lite, could you suggest a method to flash the "recovery" section only through this software? (I'm guessing an XML file should be enough, but I don't know how to write it; format).
Hopefully I'll get speedy replies .
QuaziRandom said:
Alright, I'm new around here. I searched around a lot on the forums, but didn't find a similar problem.
Phone model: Motorola Defy XT (XT535)
Carrier: It's GSM. So, it doesn't matter, does it?
I found many threads talking about the rooting process of Defy XT, and some of them did help me conduct it without problems. I did meddle around for some time after rooting; Eventually I thought I will change the stock ROM (GB - 2.3.7).
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
I tried...
Srika said:
QuaziRandom said:
hi i have faced same problem with my defyxt when i was testing cwm like you i got same error
the solution is just flash the sbf files by using rsd lite dats it bt you will lost your data
Click to expand...
Click to collapse
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
QuaziRandom said:
Srika said:
Yes... I was trying since yesterday. I was thinking of making a custom SBF to flash the recovery partition with the original one, but seeing the responses on this thread, I decided to cut to the chase and flash it with the Chinese ICS instead (and lost all my data of course). I succeeded to get my phone back up and running, but now, I have nothing but the bare minimum on it. I am trying to root and it, and get all my required apps back.
I still would prefer getting CWM recovery on this. Will keep trying...
Click to expand...
Click to collapse
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
Srika said:
QuaziRandom said:
Yep i have succeded to extract our stock recovery image and stock kernal
I have tried to make a cwm by koush website script bt it showed me a fail
Click to expand...
Click to collapse
any other way to backup my stock rom b4 flashing the new ics rom?
Click to expand...
Click to collapse
Please ask all questions in the Q&A section. Thread moved there.