[Q] Psfreedom 0.3.1 recovery help - Desire HD Q&A, Help & Troubleshooting

I bricked my ps3 a few months ago trying to revert from DEX to CEX but I forgot to clear the QA flag after downgrading, and I just got hold of a Desire HD, flashed the psfreedom 0.3.1 recovery and tried to boot to factory service mode but no luck, keep on getting the 3 beeps, is there an app to use for FSM? it's not easy to get a FSM dongle like E3 here and I don't trust ordering online. Any help appreciated

crossmission said:
I bricked my ps3 a few months ago trying to revert from DEX to CEX but I forgot to clear the QA flag after downgrading, and I just got hold of a Desire HD, flashed the psfreedom 0.3.1 recovery and tried to boot to factory service mode but no luck, keep on getting the 3 beeps, is there an app to use for FSM? it's not easy to get a FSM dongle like E3 here and I don't trust ordering online. Any help appreciated
Click to expand...
Click to collapse
ok, PS3 has nothing to do with this....what is psfreedom 0.3.1 recovery?? where are the links? I have never heard of that recovery....is it for your device?

glevitan said:
ok, PS3 has nothing to do with this....what is psfreedom 0.3.1 recovery?? where are the links? I have never heard of that recovery....is it for your device?
Click to expand...
Click to collapse
it's a recovery released a few years ago for some devices with a certain qualcomm usb controller that could be manipulated in order to fool the ps3 into factory service mode and flash a different firmware and bring back linux capability (feature was removed in firmware versions over 3.56), there are some programmable usb sticks and even some scientific calculators that do the trick, on the hd2 there was a kernel and a script that made my life easier but I have since broken the damn thing and haven't been able to get my hands on one in a fair price (or the first HTC Desire).
Anyhow, if you haven't heard of it then you probably can't help me
here's a link but if you browse the net you'll find more stuff
http://psfreedom.com/downloads.php?cat_id=2&rowstart2=30
http://www.eurasia.nu/modules.php?name=Downloads&d_op=search&query=psfreedom

crossmission said:
it's a recovery released a few years ago for some devices with a certain qualcomm usb controller that could be manipulated in order to fool the ps3 into factory service mode and flash a different firmware and bring back linux capability (feature was removed in firmware versions over 3.56), there are some programmable usb sticks and even some scientific calculators that do the trick, on the hd2 there was a kernel and a script that made my life easier but I have since broken the damn thing and haven't been able to get my hands on one in a fair price (or the first HTC Desire).
Anyhow, if you haven't heard of it then you probably can't help me
here's a link but if you browse the net you'll find more stuff
http://psfreedom.com/downloads.php?cat_id=2&rowstart2=30
http://www.eurasia.nu/modules.php?name=Downloads&d_op=search&query=psfreedom
Click to expand...
Click to collapse
that stuff is from 2010, have you checked that the partition still works with newer hboots? it has been a lot going on since 2010 in these forums...if your device boot in hboot try flashing CWM or 4EXT recovery and see if it revives.

glevitan said:
that stuff is from 2010, have you checked that the partition still works with newer hboots? it has been a lot going on since 2010 in these forums...if your device boot in hboot try flashing CWM or 4EXT recovery and see if it revives.
Click to expand...
Click to collapse
my problem is that I can't put the ps3 in factory service mode, I'm not trying to flash a rom or a kernel or something, for that I will flash twrp as I like touch recovery from 2013 lol, the recovery itself appears to be functional, I haven't got the slightest idea if it actually works (communicate with the phone's usb controller and give the command to the ps3 to go to FSM) cause you mentioned that hboot changes might affect it. Being s-off could I revert back to a 2010 hboot? I don't mind full wiping my phone, after so many years of testing I ended up using only a few apps I actually need and all the rest is either on my sd card or on the cloud.

crossmission said:
my problem is that I can't put the ps3 in factory service mode, I'm not trying to flash a rom or a kernel or something, for that I will flash twrp as I like touch recovery from 2013 lol, the recovery itself appears to be functional, I haven't got the slightest idea if it actually works (communicate with the phone's usb controller and give the command to the ps3 to go to FSM) cause you mentioned that hboot changes might affect it. Being s-off could I revert back to a 2010 hboot? I don't mind full wiping my phone, after so many years of testing I ended up using only a few apps I actually need and all the rest is either on my sd card or on the cloud.
Click to expand...
Click to collapse
No...flashing a froyo hboot will definitely mess your device. Won't brick it but it will be a pain in the neck to fix it.

Yeah baby!!! Solved!!!
glevitan said:
No...flashing a froyo hboot will definitely mess your device. Won't brick it but it will be a pain in the neck to fix it.
Click to expand...
Click to collapse
Just fixed it!! the recovery I had was apparently a TEST one, I tried another/newer version I found somewhere else and it worked like a charm...
Thanks mate, you didn't exactly tell me what to do but your hboot mention gave me the idea to try and find another version of the recovery -if possible- and I did it. Had a HUGE piano black (it's the first and most beautiful model of ps3) paper weight laying in my room for months, now got it to working again!

Related

Problem with alot of heros and no fix found USB/ADB

i have seen a problem with alot of heros and mine, to do with when it is connected to computer the drop down menu doesn't appear for sync or mount sd card. i have tried everything and nothing works, the only way you can connect to pc is through fastboot i've tried to -
- checked enable debugging
- update my recovery (thought it was a bad flash)
- reflash radio roms (thought it was a bad flash because someone else had this problem)
- updated hboot
- updated roms
- tried a few different usb cables
- drivers up to date and reinstalled ( mojos post) edit
anyone know what i could do to totally wipe my phone and start again? like original radio, rom, hboot, recovery. thanks in advance for help, i know quiet a few people could do with the help.
Solution found!
i dont know how it worked but it did,
- i installed a 2.1 eris rom which got things rolling on the phone
- installed the new htc sync that was taken from the legend in this post! http://forum.xda-developers.com/showthread.php?t=653351
- returned back to madaco 3.2 and works perfectly!
Try re-installing the drivers on your computer.
hmm maybe a stupid and too simple suggestion, but are you using any kind of task killer app ? try ignoring the pc sync process,
worked for me,
regards Wouter
Sparra said:
anyone know what i could do to totally wipe my phone and start again? like original radio, rom, hboot, recovery.
Click to expand...
Click to collapse
Install an RUU.
Regards,
Dave
Sparra, i'm having this problem also. Extended discussions have been happening on Modaco too.
foxmeister: you can't instal an RUU if you can't get the phone connected via USB
thanks people, going to try killing pc sync task dont think it will work though maybe will, yeah cant install ruu because phone doesnt connect to computer if you look at OP.
i had the same problem with my phone, had to send it in for repair as even after flashing the RUU update in fastboot i couldnt get anything
crashd said:
Sparra, i'm having this problem also. Extended discussions have been happening on Modaco too.
foxmeister: you can't instal an RUU if you can't get the phone connected via USB
Click to expand...
Click to collapse
there is a thing call micro sd card reader.
before ur phone crash do u did a nandroid backup? if u do pls try restore to the previous one =)
i would of done this but my original nandroid backup was lost!! , wonder if anyone elese has an original unbranded nandroid backup? would be good to try.
From what I can see, you CAN flash roms (updated recovery/hboot etc). ADB is working?
My guess is that you're using one of the Eclair based roms, in which usb-pc didn't work.
Try downloading mountusb from the market.
Yeah sorry i can flash roms through recovery, but no adb, computer doesn't recognise the phone.
I can connect in fastboot and all works to pc in that, I have modaco 3.1 and have used all versions of his Rom, problems started around version 2.5 or so.
Ive also tried mount usb! Might have to send back to htc!
If you put your phone into fastboot and connect, can you then run an RUU against it?
Regards,
Dave
Try another computer and see if it works
If your doing this at work, a lot of companies stop the USB ports from working.
Tried another computer and doing the ruu in fastboot, its my home pc so all usb ports work, ok pretty sure its the phones software and not a hardware problem! Thanks for suggestions!
Yeah. It's a software issue, as you can use the HEROIMG.ZIP method (search here or modaco) from the microSD when you hold vol.down + power. You also get normal fastboot. So no hardware is broken
But... Nothing I've seen mentioned can fix it. Flashing seems to do nothing. I guess there is some NAND somewhere that needs a wipe/reflash (probably the same NAND that stuff like the IMEI is stored in, but that's just a guess at the architecture). If we could find the NAND, we could compare a dump between a broken and working phone and see...
Yeah sorry i can flash roms through recovery, but no adb, computer doesn't recognise the phone.
Click to expand...
Click to collapse
it doesn't see it or says "no drivers found"
which os are you using
i can charge and usb mount even without drivers ...
It doesn't know what it is so doesn't install correctly. It's Windows 7 I don't have an issue with the druvers it worked fine before.
See http://android.modaco.com/content/h...om/300825/usb-device-not-recognized-solution/ on modaco. It's worth a shot, but bear in mind I think it will wipe /data. Might be hard to do a nandroid before though with no SD (as many people experience with this issue)
Well, I have the same problem with my hero and I have original rom, my hero isn't even rooted...

Full complete tablet backup using NVFLASH/ APX mode in the works

ElocityA7 has the option so far in the kernel, to reboot into APX mode, enabling support for full control of the tablet memory.
and in cases where needed, a full partition restore is possible.
it will even be possible to re-partition the device to suit other needs if you wish.
right now im working on a image for full recovery, but as i can only activate using a kernel with support and using a adb connection. any information on the button combo to activate it is appreciated..
otherwise its less usefull in a "bricked" situation, if we cannot start directly in APX mode.
but its confirmed for now, that the system partition is 573MB in size, and i made a full dump of it.
Advent Vega distribution pack is used for binary compatibility on windows to install it for now, but it should work just as good from linux, as Nvidia distributed the same applications for linux.
If you already got the APX setup in place,
the magic "reboot" method is entering this in a shell:
echo 1 >/proc/naz10_diag/force_recovery​and the device goes into APX mode.
ill update this thread when i know more, or got a key combination to activate directly without use of the shell command. (which is very important too)
you can read more about the APX mode here
EDIT; sorry, wrong thread.. can't delete it >.<
dexter, you did see this right?
http://forum.xda-developers.com/showpost.php?p=11758575&postcount=14
Elementix said:
dexter, you did see this right?
http://forum.xda-developers.com/showpost.php?p=11758575&postcount=14
Click to expand...
Click to collapse
yes, i think this thread started it.. and i do have a full backup, but im not flashing it so if its fully working or not, is waiting for a hardware trick to open APX mode without software.. if its not possible im not testing unless its broken somehow..
Dexter_nlb said:
yes, i think this thread started it.. and i do have a full backup, but im not flashing it so if its fully working or not, is waiting for a hardware trick to open APX mode without software.. if its not possible im not testing unless its broken somehow..
Click to expand...
Click to collapse
Elementix pointed to hardware trick. But what we can do except full backup/restore?
5[Strogino] said:
Elementix pointed to hardware trick. But what we can do except full backup/restore?
Click to expand...
Click to collapse
sorry, i did NOT actually read more than the CODE part LOL
thanks, thats a nice trick, so yes, you can do a lot of magic and still return it to a full state with the toothpick..
so like on Folio AC100, they installed debian linux and ubuntu..
in our case we can at lease play with repartitioning it.. at least resize..
but you can recovery whatever change, as long as it works..

[Q] AlpharevX, not working... [SOLVED]

Ok I'm a HTC noob so please bear with me. I setup adb-sdk environment and windows environment variable. After that I obtained Alpharevx and ran it. Everything went fine and I entered the beta key. But then after
'Beta key accepted - thank you for participating!'
, nothing happens. It just stops. Any idea how to get this thing going?
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
JWhetstone02 said:
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
Click to expand...
Click to collapse
Thanks
Yes my phone is frogyo.
Yes it's in USB debugging mode.
Yes ran as an admin because I disabled the protection so basically all apps as admin on my windows 7.
I've read in the AlphaRevX thread where some people have had to do it multiple times before it Roots their phone. Maybe try that?
Thank you. I will try more :O I hope this won't brick my phone. I heard HTC devices can't recover from brick. With SGS you could just odin back from whatever mess you are in.
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
4GivenByChrist said:
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Hey, so I am new to this board. I myself have a Dinc2 arriving soon. My brother just got his. We are both former fascinate owners. After researching and following some how to's, my brother was rooting his phone and he got stuck while attempting to get recovery after S-off. He cannot post, but here is what stated happened:
Hey I'm having a problem with my incredible 2.
Before activating the phone (avoiding the 2.3 update) I tried rooting my phone.
1) I downloaded alpharedex and generated the code
2) downloaded the recovery mode application onto the phone
3) and placed the SU zip folder onto my phone
I was stopped at step 3 because the volume down power button procedure was not working. Instead the phone powered on normally. I attempted it many more times and it would not work.
After spending some time on it, I said screw it, I just want to use the phone. So i activated it and OK'd the 2.3 update. It shut down my phone and began to download the file but it was stopped with a exclamation point in a red triangle. I tried doing a hard reset (volume up and power button) but that did not work. So i was forced to take out the battery. When I powered up the phone again, it continued the download: the phone shut down, it began to download and froze up like last time.
Click to expand...
Click to collapse
Okay, so yes I know he shouldn't have done this. After consulting with me, I was able to get him into recovery by attempting the volume down + power procedure about a dozen more times.
Should he install the super user package and reboot? Or should he do something now to fix the OTA auto reboot problem while he still has recovery?
Edit: Because he is in recovery, could he just factory reset and flash a new rom? Apparently, when he boots the phone normally it gets to the home screen and then instantaneously reboots and attempts to install the OTA. That is where it locks up.
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
k_nivesout said:
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
Click to expand...
Click to collapse
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
deaffob said:
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Click to expand...
Click to collapse
You have it working yet? If not I would uninstall the drivers you got and then download and install HTC sync. Then uninstall just htc sync leaving your drivers. Then try again. That wokred for me when I was unlocking a friends phone.
Sent from my Incredible 2 using Tapatalk
deaffob, you seem to be pretty computer literate, if it keeps giving you issues, boot ubuntu from a flash drive and do it that way. I messed with windows for a couple hours, and it took me all of 20 minutes to install ubuntu to my flash drive, boot into it and root.
bik2101 said:
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
I fixed it by going to alpharev IRC and got a great help from attn1! He was very helpful late at night.
To those of who'd like to know, this was my situation:
-Windows 7 64bit with admin control turned off=everything has admin rights.
-Fastboot off(tried on too)
-installed HTC Sync's driver.
-tried HTC driver that's posted on AlpharevX's website.
-HTC Sync was uninstalled.
-It was froyo
-Correct HBOOT(obvious because the whole point of getting the beta key was to prevent someone using the hack with the wrong version of HBOOT)
-Tried 3 different USB ports.
-ADB SDK was installed
-JDK was installed
-environment variable path for ADB SDK was set.
-tried reinstalling the HTC Driver twice, each time uninstalling with Revo Uninstaller to clean up registry.
So even after all these, the hack still did not work. So attn1 suggested that I should try it different computer or download the flash version of Ubuntu and try it in there. I tried it on my old lap with Windows 7 64 installed. I haven't used the laptop that much so the Windows was pretty clean and new.
It worked on that laptop. The lesson is, no matter how much you take care of your windows system, I practically baby my computer and do everything to keep the optimum performance, it will get screwed up after some time. I would've never thought that it'd be my desktop Windows that was the problem.
So if you are having a problem, please try Ubuntu as that's probably the best bet.
PeterGunz said:
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
Click to expand...
Click to collapse
but there's still the problem of not being able to turn fast boot off, which i think is needed to be able to get into recovery..
get into recovery
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
+1
Yep! And I'm happy I made the switch, the SLCD screen is not bad and has more accurate color reproduction and plus who uses the SAMOLED at 100% brightness anyways..-nobody really lol.
Also HTC sense imho is waay more useable with good functionalities like the ever so good integration of Facebook compared to TW. I still can't get over that since I was conned into thinking that the Fascinate had in-app pictures but atlas it was a link to the website.. whereas HTC has that and more plus notifications!
Sorry I'm just thoroughly impressed especially since this is my first HTC Device. ^__^
Plus the rotating capacitive buttons is just super cool... :3 Now to make it work when using the camera app... >.> Anybody know if this mod exists yet?
Sent from my ADR6350 using XDA App-Dinc2 switched from a Fascinate.. :3
michaelbsheldon said:
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
Click to expand...
Click to collapse
You can download a program from the Market called quickboot It allows you to reboot into recovery without doing a battery pull. this is what I use right now in replace of the 4-in-1 reboot menu
I just got su on mine. I am an Android beginner so my experience may help. My system is a laptop running Win 7. I had installed synch and then following advice removed it with all drivers. I installed the htc USB drivers, and plugged in the phone in the proper mode. AlphaRevX will not work. So (this may be vital) reinstalled synch with drivers. Then removed synch. Got AlphaRevX to do its thing at once. So the other drivers must be there!

[Q&A] [RECOVERY] CWM Recovery 6.0.5.1.2

Q&A for [RECOVERY] CWM Recovery 6.0.5.1.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Full backup of one AFTV and restore on another
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
modstore said:
I'm not sure if anyone has tried backing up one Fire TV and restoring to another, but I just tried it, and all seems good.
Doing the restore though, changed the registered account to that of the backup. So I'm not sure if it would have been registered properly, probably not. But I changed it to the account I wanted it registered too, and all seems good now.
Click to expand...
Click to collapse
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
eville84 said:
It's great to see that modstore was able to clone an AFTV.
I dont understand what modstore is saying here:
Changed what registered account? Does this mean that the new AFTV was setup to have the same amazon account as the backed up AFTV before the restore took place on the new AFTV?
I really want to be able to clone. It sounds like its possible, I just want to avoid the trial and error if possible. I'm sure others are interested in the procedure too.
Click to expand...
Click to collapse
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
nyder said:
Yes, from what he said that the registration info went over with the backup. If you want to clone machines, then this will work.
he didn't want to clone machines, so he had to put in the correct register info on the machine he put the backup on.
Click to expand...
Click to collapse
There might be a way to make it trigger the initial Registration page after doing a restore of a clone. I'll add it to my list and maybe come up with a special update.zip that will make it happen.
So if you have a FTV set up with xbmc etc you can make a direct copy of it into a stock FTV, thus cloning it as said above?
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
hellot1M said:
I've looked around and can't seem to find what to do. I've used adb before but have never ran into this issue yet seems so silly.
When I type "su" in adb shell i get this error "system/bin/sh: su: not found"
I've googled and all I can find is reinstalling the superuser on the phone... I'm trying to unlock the boot loader
Click to expand...
Click to collapse
You need root first. What fw are you on? If it's a rootable version, do that first and then follow the guides for updating here.
Yea figured it out. I'm on 1.3.0 this sucks. I'm trying to sell my amazon box to get a nexus player. Amazon has no idea how to run a home media center.
Thanks!
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
patt2k said:
Bricked mine. Cant boot into recovery anymore using keyboard. Any tips ?
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
0p3nsrc said:
What guide, and which step of said guide, were you running through that you bricked it?
Sent from my TARDIS
Click to expand...
Click to collapse
Guide from AFTVNEWS.
I got recovery to work everything was fine I could reboot from recovery back to recovery again (CWM) but after I did factory reset in CWM it gets stuck on amazon logo.
The reason I did factory reset was because of Error.7 in CWM I had that few times when flashing different roms on different phones/tablets
sometimes getting older cwm or simply factory reset would help.
So now it gets stuck on Amazon logo the keyboard trick to get back into CWM does not work anymore.
Anything else I can try before I call up amazon hoping they replace it ?
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
0p3nsrc said:
I can honestly say if you followed rbox's custom recovery install guide, used his recovery image, and made sure the md5 matched, you shouldn't have had any problems.
Out of curiosity, do you have an external hard drive plugged in?
Sent from my TARDIS
Click to expand...
Click to collapse
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
patt2k said:
Yea I did follow instructions correctly. And no I do not only had the usb keyboard plugged in so I could get into recovery.
Almost every device I rooted w/ custom recovery gave me Error 7 tablets phone etc.. I seem to have bad luck with that error lol.
Since I was on the very last step.. flashing rom -> getting error 7 grr
Click to expand...
Click to collapse
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
0p3nsrc said:
I think cwm still has some issues. It works fine for installing rbox's pre-rooted ROMs, but I can't backup my ftv. It always errors out.
Was this the first time you've gone through cwm install? Did you try installing one of his custom ROMs and then got that error? Did you verify that your recovery download went okay? Check the md5 against what's listed on the site.
I know it's a lot of questions, but I'm just trying to delve deeper to see what may have caused your error.
(I'm tech support, so I've always got more questions to ask )
Sent from my TARDIS
Click to expand...
Click to collapse
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
patt2k said:
Yes sir everything was checked few times. Bunch of times made sure even file size is correct etc...
I did install recovery however at first when I had wrong firmware I installed via ADB SHELL then I Downgraded to unlock bootloader after I downgraded I installed recovery via adbfire I think newest version .17 however it was still the newest firmware of recovery anyway.... and yepp it was stock pre-rooted latest firmware that ends with "0" that did not require the fire tv boot menu.. but now I am thinking if I had the boot menu I could have got into recovery! so AFTVNEWS mis-lead me on this part... the bootmenu would be great on all firmwares actually.
Click to expand...
Click to collapse
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
0p3nsrc said:
I'm not sure about adbfire anything. I do all mine through Linux/android terminal/windows command line. The boot menu works on firmware 51.1.4.0. When it's sitting at the logo, have you tried connecting via adb, just to see if it initialized enough to poke around? (not sure if it works that way with ftv, but I'd try, regardless)
Sent from my TARDIS
Click to expand...
Click to collapse
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
patt2k said:
As far as I saw I could only connect via adb at least when in recovery mode.. otherwise it was a no go... anyways thanks for helping me out. I think there is no rescue in this situation by somehow fixing it. I mean just wanted to have few features like swap storage with a flash drive and have newest FW. But that's ok.
Thanks for your time!
Click to expand...
Click to collapse
Sorry I couldn't be of more help :/ the issue you'll probably see is that unlocking the bootloader voids any warranty with amazon.. So I'm not sure what amazon may or may not do for you.
Sent from my TARDIS
About the possible Lollipop ROM for FireTV,is there a way to get the latest qualcomm Adreno 320 drivers like [email protected] from another device for flashing in proper FTV directories since it is meant for Lollipop?
I am hoping for the fix for Dolphin to be runnable and Reicast to no longer cause reboots,as well as better performance for things like Mupen64Plus AE.

Blu Advance 4.0 L A010U ROMs

Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy

Categories

Resources