In my case after moonshining 5 times or more , my DNA got hang/stuck no response at all and status in PC waiting for device.
I have to press power button until power off and start up again.
That alway happened like that (i tried more than 10 times with same result) , looks like moonshining never finished its job,
because my DNA always get stuck. In hboot status is TAMPERED and LOCK
I have tried revone but always got error 2 result.
Now got stuck with firmware 2.06 and on android software number 1.15.605.4 710RD
I tried to return to firmware 1,15 so that could flash to StockRUU 1,15 but failed
D:\Android>fastboot flash zip PL83IMG.zip
sending 'zip' (434 KB)...
OKAY [ 0.201s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Afterwards now wifi I to died after trying moonshine-s-off, I have tried factory the re-set but wifi continue to error
Please help what should i do.
Sorry for my bad english.
HBOOT-1.33.0001
RADIO-1.01.04.0308
Ruu
Sent from my dlx using XDA Premium 4 mobile app
Jaggar345 said:
Ruu
Sent from my dlx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Could not the Ruu, because of stock of the ruu only had the version 1,15
pisang_aza said:
Could not the Ruu, because of stock of the ruu only had the version 1,15
Click to expand...
Click to collapse
Sounds like you have the same issue i am. Check my thread out and follow it. So far ive been stuck though. got a warranty claim though and got my new DNA. i have 2 more days before i have to send this one back
http://forum.xda-developers.com/showthread.php?t=2552804
Related
Hi!
Yesterday i managed my Flyer to S-off via revolutionary tool.
Today i wanted to update to Honeycomb with this tutorial:
+
Google search: android.modaco.com Installing Honeycomb on your Flyer
Guide from Paul.
i got now stuck after the htcdev bootloader unlock.
i should transfer the cwm recovery file via fastboot into the flyer
command: fastboot flash recovery revolutionary-cwm-4.0.1.4-flyer.newhboot.img
Code:
< waiting for device >
sending 'recovery' (4682 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.198s
Why this is failed? i tried to do the next step, getting into clockworkmod recovery but nothing happens.
My Flyer shows now:
Code:
*** RELOCKED ***
*** Security Warning ***
FLYER PUT SHIP S-ON RL
HBOOT-1.11.0006
MICROP-0950
RADIO-3821.08.00.26_M
eMMC-boot
Aug 29 2011, 13:32:02
Fastboot 9v AC (because charging)
VOL UP
VOL DOWN
POWER
Bootloader
reboot
reboot bootloader
power down
What can i do now? any idea?
edit: adb don't work, fastboot works.
I'm going crazy tried to reunlock bootloader via htcdev. When i flash the unlock token i get same error
Code:
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.015s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.019s
Why in the world would you use the htcdev unlock? Go to flyer development and follow globatron's honeycomb guide. Much better than voiding your warranty.
Sent from my PG86100 using Tapatalk
i did yesterday exactly those steps from globatron for soff and cw recovery.
For getting Honeycomb i used another guide yesterday.. because i found this site today..
I really dont know what to do now
Worst case run ruu of your stock software
Sent from my HTC Flyer P510e using xda premium
somehow it doesnt work
C:\Users\h0f1\Desktop\htc\android-sdk_r15-windows\android-sdk-windows\platform-t
ools>fastboot flash untlocktoken Unlock_code.bin
sending 'untlocktoken' (0 KB)...
OKAY [ 0.013s]
writing 'untlocktoken'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.017s
edit:
made it now with other version of fastboot... this is crazy..
so i unlocked again and now i can go on with the other steps?!
I would return to stock then use globatrons update method. Do you know your stock ruu
Sent from my HTC Flyer P510e using xda premium
is going back to stock via ruu possible when i changed hboot, radio and boot file?
the guide from paul says:
Do NOT under any circumstances run the RUU in it’s entirety nor ‘fastboot flash rom.zip’ – this will make irreversible changes that you don’t want!
Be careful if you flash any RUUs or do anything that could revert you to S-ON on a broken system – this could leave you stuck
i think i will recharge and go through the last 4 points..
im afraid
Try to get a new unlock token.
I can not see why running your ruu to stock.would be an issue but I am not 100% certain. I did a revert last week and the only thing I needed to do prior was relock hboot first which you are already locked.
Sent from my HTC Flyer P510e using xda premium
first i wanna say thanks for your help!
i did today the last two steps after recharging the battery.
last 2 steps are putting the new image onto sdcard via adb and second step was factory reset und dalvik wipe. All two steps worked fine for me, but after restart the flyer is going to a bootloop.
what should i do now?
Should i get back with the RUU?
Can i setup honeycomb after getting back with ruu with the tutorial from globatron?
best regards
tom
did you flash the zip through recovery
Sent from my HTC Flyer P510e using xda premium
^the tutorial say get into clockwork recovery mode and type into command "adb shell mount /sdcard && adb push stock-hc-flyer-system.zip /sdcard/"
this command finished after 3 minutes and i was also lookin at the sd card the file is on the sd card.. after this i wiped dalvik and made a factory reset in the clockwork recovery mode. Afterwards Reboot -> then bootloop
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
h0f1 said:
lool is it possible that i have to " install zip from sdcard" ? if yes i'm the dumbest flyer user on the world *g*
edit: i tried now to install the update via recovery, it says E: Can't open /sdcard/stock-hc-flyer-system.zip (bad)
Click to expand...
Click to collapse
Re-download, it's corrupt.
ikingblack said:
Re-download, it's corrupt.
Click to expand...
Click to collapse
+1
Sent from my HTC Flyer P510e using xda premium
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
h0f1 said:
really i promise i will neveer ever never try to flash/hack/root anything. its just horrible thinking all the time you brick it or anything else xD
i tried to reboot bootloader via adb in the recovery mode, flyer turned off and now nothing happens. cant go into bootloader or something else.. trying to recharge again, maybe battery is low again (i hope..)
well i will go on tomorrow evening.
great work guys anyways, thanks
tom
Click to expand...
Click to collapse
I don't know if it's possible to really stop it from booting or displaying anything on the screen. Recharge and once it's done hold power button for a long time.
Good Luck
help fully bricked htc flyer p510e
here is what i did step by step:
bought an htc flyer, then upgraded it officially to honeycomb
i did not like honeycomb so i unlocked bootloader with htc dev method
then flashed recovery and rooted....
changed the misc_version and downgrade back to gingerbread with fastboot flash zip rom.zip
it worked........gta 3 and gta vice city worked.......few months later the gta 3 and vice city started crashing( just like honeycomb)
so i got s-off with revolutionary.....and flashed honeycomb PG41IMG.zip
that worked...........few months later i wanted gta back so i could not take i tried flash back down but did not work...it would get stuck in RUU mode ...so i flashed PG41IMG.zip back and that worked ..i was not bricked...so i tried another method
i flashed fastboot express downgrader.nb0 and
flyer downgrader.nb0
then changed gingerbread rom.zip to PG41IMG.zip and placed it on sd card
went into bootloader and let it flash
the bootloader at this moment:
***security warning***
pvt chip s-on
hboot 1.10.000
..................
it does not show whether the bootloader is locked or unlocked......no recovery.......tablet does not boot.....only to bootloader and fastboot.....
i tried to flash the unlock token for bootloader but get
signature failed error....
i tried to flash the honeycomb PG41IMG.zip but get
checking header failed
remote[signature failed]
cant flash anything because of that ...cant flash recover to even turn off the verification signature check.....
plz help ...whether you help me to fix it back to gb or hc to dont care ..just want it to work
plz help me fast
battery charges but phone goes into fastboot .....
plz help
just ask if u need more information on the situation..
plz anyone
Should probably find a good RUU that is compatible, create a gold card and do a clean re-load of compatible ROM.
hey just wanted to ask for some advice... been searching for a while and having a hard time finding answers... has anyone ever relocked a rezound (fastboot oem lock) and had it say the following:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
then in hboot, it says ***TAMPERED*** and ***RELOCKED***
and any attempt to run an RUU results in:
Hboot Version is older!
Update Fail!
im having a hell of a time, and ive returned to stock before and never had this problem... any advice would be greatly appreciated
thanks everyone.
CPTfixt1on said:
hey just wanted to ask for some advice... been searching for a while and having a hard time finding answers... has anyone ever relocked a rezound (fastboot oem lock) and had it say the following:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086008 (0x7FDFD78)
FAILED (status read failed (Too many links))
then in hboot, it says ***TAMPERED*** and ***RELOCKED***
and any attempt to run an RUU results in:
Hboot Version is older!
Update Fail!
im having a hell of a time, and ive returned to stock before and never had this problem... any advice would be greatly appreciated
thanks everyone.
Click to expand...
Click to collapse
I'll assume your s on right? You can't ruu back to an older firmware version unless you s off.
Not sure about the first error though
Sent from my Rezound using xda app-developers app
Squirrel1620 said:
I'll assume your s on right? You can't ruu back to an older firmware version unless you s off.
Not sure about the first error though
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
yes i am (couldnt get s-off to work lol) but i tried with the newest RUU, which i was upgraded to before i rooted/unlocked... ive even relocked this phone before and didnt have an issue.
i think ive accepted the fact that i cant fix it (i wanted it stock for warranty replacement reasons) and im already in the process of getting my hands on a GNex
CPTfixt1on said:
yes i am (couldnt get s-off to work lol) but i tried with the newest RUU, which i was upgraded to before i rooted/unlocked... ive even relocked this phone before and didnt have an issue.
i think ive accepted the fact that i cant fix it (i wanted it stock for warranty replacement reasons) and im already in the process of getting my hands on a GNex
Click to expand...
Click to collapse
99% of the time, they won't care about the bootloader status. I've never heard of them denying a replacement for it.
Sent from my Rezound using xda app-developers app
nevermind guys, just picked up a Galaxy Nexus. thanks for the help tho :
CPTfixt1on said:
nevermind guys, just picked up a Galaxy Nexus. thanks for the help tho :
Click to expand...
Click to collapse
Awesome, I'm picking my wife up a GNex when my tax refund comes in. Should be fun
Sent from my Rezound using xda app-developers app
I purchased a EVO 4G LTE for my sister a little while back and recently she had her boyfriend attempt to root it for her, and since I'm here it obviously didn't go over all too well. All he said he did was follow a video (which he gave me) on how to root for the newer software version. "Something happened and it didn't work so I watched another video and tried that" The phone is currently unlocked with S-ON and he flashed a working version of TWRP and cm10 couldn't figure it out and here we are. help please. Rooted using Linux. i did some reading and found out i had to flash the boot.img through fastboot. it just hangs at <waiting for device> in the terminal. Apologies if this has been answered, if so please point me in the right direction.
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
BusstopBill44 said:
I forgot to mention I too am running linux, i tried to open this in wine and it wont save the files to my system. i will try this at a friends house asap and report back, thanks
Click to expand...
Click to collapse
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
jesuscash said:
Is adb configured right?
I use Linux and when I was son I was able to flash boot.img without problems
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I'm not really sure what he did or why he even tried. How can I check adb to see if that was done correctly?
tilltheend714 said:
http://forum.xda-developers.com/showthread.php?t=1917106
Scroll down to see how to replace the files with the files from the cm10 rom that he flashed to the phone.
Click to expand...
Click to collapse
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
BusstopBill44 said:
Alright, we have made some progress, I went to a buddys house and flashed the boot.img using said method flashed gapps as well.Now, i have no touch function but it does boot to the homescreen, any advice?
Click to expand...
Click to collapse
Boot into bootloader and check the radio. If its 1.12.11.1210 then he took the 3.16 OTA and your only choices are what premo15 said.
premo15 said:
I'm guessing it's on the latest firmware (3.16)? That update breaks the touch panel on all non-3.16 roms (which would include cm)...the only way to downgrade is to flash the tp.img from the previous firmware (3.15), which requires s-off. I would recommend going that route as it makes things a lot easier. For example, once you're s-off you won't have to fastboot flash kernels anymore. Check out the dirty racun thread in Original Development for more info. If you decide to s-off, you can flash the old tp.img zip from the 3.15 firmware to get the touch panel working for cm: (Had to remove link)
Otherwise, if you don't want to go s-off then you'll need to flash a sense Rom that's using the 3.16 base (which I think most if not all are now). I recommend Viper4g, runs great and has tons of tweaks like cm.
Sent from my EVO LTE
Click to expand...
Click to collapse
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
BusstopBill44 said:
Thanks, i decided to try and go S-OFF. I flashed the correct RUU for 3.16 and I get an error message after I flash the RUU,zip
/RabiesShot_LINUX$ sudo ./fastboot flash zip RUU.zip
< waiting for device >
sending 'zip' (659905 KB)...
OKAY [ 45.943s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 122.961s
Click to expand...
Click to collapse
Did you run babyracun before relocking and running the ruu?
tilltheend714 said:
Did you run babyracun before relocking and running the ruu?
Click to expand...
Click to collapse
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
re-flash twrp
bigdaddy619 said:
re-flash twrp
Click to expand...
Click to collapse
another error, $ sudo ./fastboot flash recovery openrecovery-twrp-2.4.2.0-jewel.img
sending 'recovery' (8032 KB)...
OKAY [ 1.277s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.107s
and tried it with 2.4.1.0, which i had before, as well.
BusstopBill44 said:
Wow, I completely looked past that, thought I read that whole page thoroughly. It looks like after I failed at that RUU it no longer has TWRP installed, I really hate asking but what can I possibly do now?
Click to expand...
Click to collapse
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again.
Click to expand...
Click to collapse
^^^^ true
I don't know if this will work since you've already tried dirtyracun; but I just used this method to achieve s off. It's ridiculously easy, and took me 5 minutes..
http://forum.xda-developers.com/showthread.php?t=2163013
tilltheend714 said:
I don't know if you can just install TWRP again or if you'll have to go through the HTCdev unlock again. You'll need the Unlock_code.bin for the Dirtyracun process anyway so you might as well get it again.
Click to expand...
Click to collapse
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
BusstopBill44 said:
alright, some progress, got my unlock from HTCDEV got the unlock token, restarted the whole S-OFF process over,got through the ruu.zip. it installed, It rebooted itself instead of allowing me to "sudo ./fastboot reboot bootloader." It booted to a stock rom (which is now 3.15), I was in shock that I had her phone working again. restarted to bootloader, noticed it was locked and s-on went back to the directions and had me unlock through the unlock_token and finall had me run "sudo ./RabiesShot...which is giving me errors.
Starting up...
Testing connection...
Test 1: Rebooting into bootloader
Waiting fastboot (18/60)
Waiting...
Test 2: Booting device...
Waiting ADB... (60/60)
Test 2: Booting FAILED
Reboot device manually
Connection test failed!
After this error I rebooted into bootloader and im S-ON with unlocked. can i jump right into s-off'ing it
Click to expand...
Click to collapse
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
tilltheend714 said:
Yeah, you should be able to run rabies shot again. Did you enable USB Debugging befor trying to run rabies shot? And are you running linux 32-bit?
Click to expand...
Click to collapse
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
BusstopBill44 said:
thanks, and after all that s-off/on nonsense I cant s-off with a 32 gb microsd....grrrr
Click to expand...
Click to collapse
You can try this
http://forum.xda-developers.com/showthread.php?t=2163013
But that requires root. You don't have a 2gb card laying around anywhere?
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
andres8900 said:
Hello Amaze thread. I flashed jose's Dark Glass ROM based off of CM10.1 and one day my phone turned off and wouldn't boot. I went into recovery and it goes into safe mode because the internal memory card is unreadable, tells me to wipe, etc. but it gives me junk errors. My issue is similar to the issue of someone else in another thread http://forum.xda-developers.com/showthread.php?t=1773723(which was resolved)], but I'm not having such an easy time fixing my problem. When I go into the bootloader and try to flash my RUU from mobilicity by changing it's name to PH85IMG, the blue bar fills up, it says "parsing..." but then it goes back to the bootloader. Does anyone know what is going wrong? Thanks in advance to all you helpful people. Sorry if I violated any rules in this post.
Details: S-OFF + bootloader is unlocked
Edit1: I read that my bootloader had to be locked in order to reflash RUU. I relocked it using Hasoon's all-in-one-tool but the zip file would still go back into bootloader after the blue bar fills up. The zip isn't parsing. I also tried using Hasoon's tool to reflash the RUU. Bootloader says re-locked (still s-off) but it still doesn't work. The CMD spits out this:
Code:
sending 'zip' (331249 KB)...
OKAY [ 32.595s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 40.896s
Click to expand...
Click to collapse
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
shubham211995 said:
In order to flash RUU you will need to be unlocked bootloader because it rejects all time when you try to flash RUU.
So first unlock it and after that try to put ruu on SDcard and then go into recovery .
It will work for sure.
Hit thanks if I helped you !!!
Click to expand...
Click to collapse
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
andres8900 said:
Hi, it still didn't work. Tried it while the bootloader was unlocked and again while it was relocked. It doesn't get past the "parsing" stage. I tried it with two different SD cards already btw and I also checked the MD5 checksum. They match. No luck for me.
Click to expand...
Click to collapse
Are you sure that your sdcard slot is working ??
Sent from my HTC_Amaze_4G using xda app-developers app
Mobilicity ruu isn't working it's a firmware zip with a update it's not a ruu... And it's not a brick.. Also a ruu can't be flashed from recovery... Flash the t mobile R2 RUU from bootloader and it'll work.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Need to take my phone back to stock as I'm taking it into Best Buy for a swap (cracked screen). I'm running the latest OTA (I think) and running Beanstalk. I tried running VipeRuu but it fails
Code:
sending 'zip' (660336 KB)...
OKAY [ 26.399s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 26.432s
I'd like to get it completely back to stock, including S-ON with a clean bootloader. Any help?
Edit: HBOOT-2.09.4444
Radio-1.13.11.0830
OpenDSP-v31.1.0.45.0815
FYI, BB does not give two craps about your phone being rooted. I completely wiped my phone to the point of there being no boot image, and they took it with no issues.
Sent from my EVO using xda app-developers app
iandmacdonald said:
FYI, BB does not give two craps about your phone being rooted. I completely wiped my phone to the point of there being no boot image, and they took it with no issues.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Yeah, I do seem to remember them mentioning that the last time I stopped in.
Either way, I did figure out what my problem above was so I'm now back on stock.