My HOX was in this rom & kernell tripndroid_endeavoru-ota-eng.noeri_002.zip
http://forum.xda-developers.com/showthread.php?t=1784185
after install tripndroid_endeavoru-ota-eng.noeri_003.zip and flash thats kernel([email protected] #2)
my device do not allow me to flash other kernel(in bootloader allow and flashing successful but in phone os show [email protected] #2) OR do not allow to lock boot loader AND in TWRP recovery all operation same as format system, data, install new rom and other operations doing successful but after reboot phone i see nothing happen, and see last rom with last kernel last and last user data;
Who know anyway to go out from read only HOX?
How did you install that rom? Because that download link was deleted i think a month ago?
the v003 noeri kernel is the culprit of that hard bug.
Basically, you are now in apx mode. you can't do anything about it, even trip whacked his phone cause of numerous failed attempt to fix it.
Sorry dude but your phone was bricked. no other option but to send it to service center. hope you are still under warranty and your provider accept the repair for free:angel:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
if i am of any help, please hit the thanks button:good:
Sorry to say this mate but you're totally bricked.
Only a new motherboard will help...
Its best to search on how to brick your bootloader properly .....when the service center can't read/boot your bootloader anymore they don't know if it was actually unlocked before. This way you have more chance of a free repair. Because when they see the tripnraver stuff they are unlikely going to fix it under warranty/hardware defects.
but my HOX not have waranty or garanti!
i think wait to s-off to solve read only problem...
I hope you get it sorted when we get s-off !
I also have one in read-only, and I've done some investigations.
I'd rather say it's the emmc controller that's busted, in which case we won't be able to do anything as long it's not functional (I don't think even the official s-off methods will work). On the other hand, while bricking, the write protection went off and I could write some partitions, until it settled to read-only (my goal, back then, was apx). I find this interesting because this might be an short (but dangerous) way to s-off. Still, we need to identify the exact commit that holds the guild.
PS: if you don't have warranty, try changing the emmc chip, might be cheaper.
Hello and greetings to all, this is my first XDA post so please be gentle with me...
I recently started pondering one of the problem's I see a lot of people surfing these Forums suffering from, the dreaded "Bricked Device"
For whatever reason generally through no fault of your own, you may end up with a bad flash that results in your device becoming a worthless but very expensive paperweight. :crying:
Some examples of people suffering a bricked device:
http://forum.xda-developers.com/showthread.php?t=2229416
http://forum.xda-developers.com/showthread.php?t=2275035
http://forum.xda-developers.com/showthread.php?t=1926098
After doing a lot of research myself from suffering something similar I started to notice the general theme is always the same, people saying "wait for the device manufacturer to release the NVFlash!"
However in these instances shown above the RETAILER in question is ASUS and they are never going to release any kind of source, to any kind of NVFlash.. Because if they did, you have to reflect that would put them out of buisness, it's far more lucrative for the RETAILER (not the manufacturer) to just sit back and wait till you've got a problem with a shody update and then push selling you a new motherboard for your device. A new motherboard that in all likelyhood you dont even need and if you send in the device for repair that you would probably never even see being placed into the device in the first place when all they have to do is fix your broken bootloader.
Because the reality is, the Manufacturer being "TEXA'S INSTRUMENTS" have already made the full source of the NAND Flash to these devices readily available to the RETAILER and there partners in buisness.
It may surprise you and a lot of other people to learn that in fact you can already download The Official TEXAS INSTRUMENTS FLASH TOOL Ver: 1.6.0.0 from the following link: http://www.ti.com/tool/flashtool
Complete with the entire walkthrough guide available here: http://processors.wiki.ti.com/index.php/Flash_v1.6_User_Guide
I know there are a lot of people out there on this forum that have been looking for this tool so I decided I would make my first post a link to the Bootloader Reflashing Tool for the majority of all ARM or OMAP based devices.
Please dont ask me how it work's, I'm happy to sit back and let those out there with more experiance in these matters take the plunge for themselves if it means in the long run we can all finally put Linux onto the Android Touch device with relative ease and recover from stupidness such as a Bricked device because of a crappy bootloader update where the RETAILER decides in there infinate wisdom to remove USB device support from the Jelly Bean Bootloader...
On the plus side, this means that in the near future when the right people get there hands on this tool (from the Manufacturer) we can all expect to see some far more funky flashing startup screens and some rad custom bootloaders :victory:
Thank you for taking the time to read my first post...
P.S: I also nearly forgot to mention this is the tool that LOCKS and UNLOCKS the Bootloader, so once people start making Bootflashes for there device to use with this tool then you wont see "Your Device is Unlocked" in your face everytime you turn on the device! (I wonder if that means we can recover our warranty, I can almost hear ASUS sqweak in protest!)
REALY Nobody knows to work with this tool ???
REALY????
I dont belive this....
I have TF300TG briked... I I want to TRY any solution...!!!!
BR
Mihnea
HI Guys. So i managed to flash the a200 bootloader on this thing a while back and installed some custom stuff. After bricking it once and having to RMA i decided to leave it unlocked. About a year later the tablet just died all of a sudden. I can get into CWM recovery but when I try to flash a rom it gives an "fail to mount" error. I did some searching and i found out that maybe the emmc is bad and would require a motherboard replacement. Well since Acer wants to charge me $250 to repair it and a replacement motherboard cost be around $30 I think i would take the risk doing a pulldown and replacing the motherboard myself, If i can get some help to do it as I wouldnt even know where to find the first screw. I'm also willing to document the process and post it as a tutorial for those facing a similar problem if it is successful. So if anyone can advise me on how to do this I would be eternally grateful.
Hey guy's,
Hopefully This is in the right place. Please assist in anyway you possibly can. This phone is not a brick, but it might aswell be. I have tried literally every kind of reset unbrick guide I can find for the past 2 months, and nothing works.
From what I can tell it is a driver issue, but even installing the meta mediatek preloader, and drivers does not seem to work. I have tried a fresh install of windows 8.1, windows 7, and xp. nothing works. I can not install the adb drivers for this device, because the phone will not even boot into recover. Recovery is corupted or something. I do have an mtkdroidtools backup, but can not flash it with sp flash because it always gives the error "THIS IS A SECURE BASEBAND CHIP PLEASE LOAD AUTHENICATION FILE". I've worked with kirito9 which was a big help in understanding a few things, but we could not get it sorted. I will stop talking now, and post something useful.
BTW:mobile upgrade tool s does not work either. I get terminal read failure.
As of now im on windows 8.1 with drivers installed. I have posted a couple of videos to show whats going on. Hopefully they will help. I can post some logs, but I honestly dont know which ones you would want, I have a lot of them, and have tried so many things I dont know where to begin again. In the zip file there is 2 videos, and the original mtk.log.
I forgot to mention that, this all started when I wanted to root, and install a custom recovery. I believe I used the guide on here but cant remember seeing as it was a while ago. Also the phone does not vibrate at all. Like I said I have a backup, but I dont remember much about it I dont know how reliable it is, and if I read back with sp flash or not. I believe I had to right? idk. thanks in advance.
https://drive.google.com/file/d/0B_DyVUIoGhqBSXlhbkNhdVNCR1k/view?usp=sharing
Wow I cant believe nobody has run into this problem. That or you guy's are just busy which I totally understand.. I'm just really frustrated. I think I am going to try to return it to t-mobile. You gotta know when your defeated, and this is it. This phone has been a nightmare.... I just hate giving up. I broke it, and I wanted to fix it.
Anyway if this was in the wrong lace to post please let me know. thanks.
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
TireIron431 said:
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
Click to expand...
Click to collapse
Hey man, I cant really help with unbricking it. Mediatek chips are not my strong point but i just wanted to say logically if the recovery is corrputed and the rom is corrupted and the bootloader is not playing ball then unless the chips have a write counter/modification check then you should be okay I reckon.
Good luck though
I still have it because I wanted to at least make it boot ok, but to no avail. I got the replacement and made a good back up with mtk droid, but I still get the error.
The phone is an Identical copy of my last one, and still no go. I even tried to flash it with the new phone, I get the same error. so I guess im a monkey, and cant do it right. If it's doing the same thing with the new phone as it is with the bricked one, than its me right?
I did notice that I cant create a scatter file with the create scatter button(its greyed out) I can only make one through the firmware.info.
This is the phone info from both phones.
Hardware : MT6581
Model : ALCATEL ONE TOUCH 4037T
Build number : ALPS.KK1.MP1.V2.10
Build date UTC : 20140918-073410
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/09/18 15:26
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Sep 8 10:47:59 CST 2014
Uboot build v : ----- should be root shell
LCD Driver IC : 0-nt35512_dsi_vdo_tdt_lcm_drv
From what I have read this is actually a 6572 chip. Is this correct? I was just thinking that maybe droid tools wasn't reading it right, or backing it up right. Droid tools creats a 6582 scatter file, but my phone says 6581, and I saw 6572. Which one is it? I cant find or make a 6581, so I do not know what to do. I have tried both phones with all of the different drivers, with the different scatters, and I always get error 5000 secure baseband chip.
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
danymt87 said:
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
Click to expand...
Click to collapse
Your issue is you flashed with the secure bootloader still active, as to why your having issues flashing it back... I've been searching around for a Custom Recovery/ROM, I'll check back in if I find anything on Disabling the Secure Bootloader, as I see it your not going to be able to restore (even to STOCK) without Unlocking the Bootloader/ And/Or Reactivating it upon re-flash.... So far no luck on finding a way to disable it, but just started a couple hours ago....
Mike
UPDATE:
ok Upon more searching it appears at the moment you need an NCK BOX...
https://www.google.com/search?q=unl...-8#newwindow=1&q=disable+secure+boot+on+4037t
http://www.ebay.vn/mo-ta-san-pham-281534386171.html
Dear tech friends
I happen to own a Biloba Redmi Note 8, and I understand now that it isn't the best phone for DIY. But I want to make the best of it as selling it will mean loss of money and overall I am very pleased with the thing. Or maybe 'was'? I hope I did not kill it.
The situation:
- it is stuck in a kind of startup loop that restarts endlesly. I need to put the phone in fastboot to give it some rest. I believe I managed to shut it down yesterday, but I do not remember how.
- this happened after I installed a (wrong?) recovery rom into the boot sector - this was before I realized how particular this Biloba version is.
- I want to fix it and put a google-less rom, perferably open source/GSI but if not possible official China Rom could be an alternative as it doesnt have Google.
My question to you is foremost: where can I obtain the knowledge to fix this myself? Ebooks, tutorials, Xiaomi service manuals? Mind you: it is BILOBA.
Also I havent found any decent MiFlash program. They all seem buggy as hell. Doesn't Xiaomi offer official tools for this?
Why is smartphone administration seemingly shrouded in mystery? Companies do not want us to amdinister our phones ourselves? PC technicalities are so much more accesible it seems?
Thanks people!
pyrkaios
same here
I guess the best places are the threads on xda on devices that have more active modders.
I usually use 'Google', and mostly keep in mind a way to return to previous conditions.
Keeping a copy of original firmware ready helps there.
Also, I tend to flash with fastboot whenever possible.
Only reason not to is when I must flash when in BROM.