Hello,
This issue is driving me crazy because I cannot figure it out for the life of me. Basically, any ROM I flash will cause a constant bootloop on the Redmi logo and I cannot get past it regardless of what I try. The /only/ things that do work seem to be DerpFest-11-Official-Beta-miatoll-20210615-0347 and earlier but NOT any of the newer Derpfest versions. Also, the only stock MIUI that will boot just fine are really old stock MIUI 11 versions from about a year ago. Latest stock MIUI (12) is a no-go.
I have a Joyeuse and I am on V12.0.1.0.RJZMIXM firmware. I never recall having this issue until a few weeks ago.
Things I've tried:
- Clearing /data entirely, fresh format, etc.
- Messing with dm-verity
- Messing with forced-encryption on and off
- Trying with and without Magisk
- Last/latest version of official MIUI 11 (Q), also bootloops
- Different versions of the MiFlash tool
- Manually flashing the latest stock MIUI 12 by typing out each command using fastboot.exe in a command prompt
- Consecutively downgrading firmwares until I'm at the first release
- Relocking and unlocking bootloader again
Basically all the generic recommendations people have posted on here, as well as all that I can think of do not work. And this is not my first phone troubleshooting rodeo, either.
Anyone have any ideas? Much appreciated. My theory for now is some unusual partition got messed with somehow, even though I recall doing no such thing.
Note: please move this posting to the international model subforum if in the inappropriate spot, thanks
You have hardbricked. Not bootlooped.
Follow these tutorials to bypass protection and restore your phone.
MTK Bypass Universal
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
Thanks to: chaosmaster / k4y0z: GitHub / XDA xyzz / xyz`: GitHub / XDA Dinolek: GitHub / XDA How to install: 1. Download the attached file: VD171_MTK-bypass.zip. 2. Extract the file and open the folder. 3. Run and install python...
forum.xda-developers.com
Flash in EDL
Thanks! I'll give it a try.
Looks like that guide is for MTK chips, not the Qualcomm ones. But that led me in the correct direction.
I found out how to get into EDL mode, but it looks like I'll have to find a patched firehose file without the auth.
Thanks.
Oops, sorry but thats good news!
Looks like I can't do anything until someone figures out how to bypass EDL authentication for my device. The only immediate option is to pay someone with appropriate credentials to do it for me, which seems like petty extortion.
So, I guess I'll wait around.
JJohnson1988 said:
Looks like I can't do anything until someone figures out how to bypass EDL authentication for my device. The only immediate option is to pay someone with appropriate credentials to do it for me, which seems like petty extortion.
So, I guess I'll wait around.
Click to expand...
Click to collapse
oh you mean mi authorized account?
You try binding your phone.
In where it says unauthorised account in the corner it says bind.
Try that and wait.
Maybe you'll get access who knows?
How'd you go OP?
Well I can't really do anything, because as I stated above, to perform the EDL unbrick I need either 1) a Xiaomi authorized account, or 2) a bypass for 1.
So far no one has figured out a bypass for this device, so the only option is to find someone with the appropriate credentials. Alas, it looks like pursuing the 1 route would cost a one-time payment. Furthermore, all the services I've seen offering said service look super shady, and I have no idea if they speak proper English.
So for now I'm just continuing to wait for a bypass or better solution.
Hello,
I have the same problem. What I don't understand is the thing with credentials. I have the proper credentials and can setup the stock firmware.
However, whenever I flash something newer than the DerpFest version from 15062021 (the one you said above) I get stuck with this booting every second. The only thing that helps then is to fire up the Xiaomi ADB Fastboot tools jar-file and re-flash the stock Joyeuse firmware.
Do I have - after on stock - somehow to turn off the credentials (and how?) or what would be the way to go?
Sorry for the questions, but I am a bit confused, what the cause of the issue is and how to deal with it.
Thanks!
I'm surprised someone else is having the same problem, to be honest.
When you say "the credentials", are you referring to the MiFlash account login, the login screen you have to log into on stock MIUI first boot, or something else entirely?
JJohnson1988 said:
I'm surprised someone else is having the same problem, to be honest.
When you say "the credentials", are you referring to the MiFlash account login, the login screen you have to log into on stock MIUI first boot, or something else entirely?
Click to expand...
Click to collapse
He is referring to the “authorized account check” like a bypass.
There might be but they are usually specific to certain phones and chipsets.
AFAIK there's no solution at the moment for Joyeuse.
Great forward thinking on Xiaomi's part -- there's only one possible solution and no one is authorized to perform said solution. What were they thinking?
Well if I was a thief. But I'm, not XD could use EDL to reset a stolen phone with a locked bootloader soooooo.
if EDL lock then basically a paperweight.
I guess I'll wait and see what happens, seeing as how I have no choice anyway. Looks like xdadevelkl also has no choice.
The other outstanding question is how did both our devices even get to this state? If it's not an isolated incident after all, that's a major problem.
Many people have the issue. If you can provide proof of purchase. Xiaomi will fix it for you.
Since we are allowed to unlock our bootloader idk if they charge but theyll do it.
There's no guarantee that the brick won't happen again though, if the issue isn't uncommon. That's the thing that concerns me.
Anyways, I appreciate the assistance.
I will post if anything changes with regards to my situation.
JJohnson1988 said:
There's no guarantee that the brick won't happen again though, if the issue isn't uncommon. That's the thing that concerns me.
Anyways, I appreciate the assistance.
I will post if anything changes with regards to my situation.
Click to expand...
Click to collapse
Bruv, I have the exact same issue as you, but miui 12 Q boots for me but that's about it, no A11 ROMs, not even official, only A10 ROMs(I tested with latest official RR)... I also gave it to service center and they maybe tried edl flash and still couldn't fix it.
Bumping my old thread because I said I would make a new post if something changed.
Well. I ended up finding a guy that performed an EDL flash for a small fee. I still can't believe I had to pay someone to do this, but I was nearing the point of throwing the phone in the trash, so.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bad news. Nothing seems to have improved. I'm still bootlooping after the EDL flash even with the stock ROM (I even tried LineageOS as well just to be sure).
So, I am just about done with this phone. I am perpetually stuck on a custom ROM version from six months ago, and nothing else works.
Related
Ok so the strangest thing happened yesterday. I left work, phone fully functional and got in the car to drive away. Where I was parked I was still getting the wifi from the building I work in and I wanted to start streaming music. I turned off wifi and tried to use the data network. No signal. Now, sometimes, it takes a really long time to switch back over to cellular after leaving wifi and especially if I use wifi calling. So, instead of waiting, I pulled the battery like I've done dozens of times before. Only, this time the phone didn't restart. The splash screen comes up and then it shows what appears to be the default android animation. I've never seen this on this phone or any of the roms I've loaded. It never starts the phone; the animation just keeps running. I couldn't get into recovery, it just returned me back to the bootloader screen.
Now when I got home I tried a few things with the all in one tool. I thought if I could load a recovery, I could re-flash my ROM and possibly get the phone working again without data loss. That didn't work. ADB couldn't even identify the device. Then, I downloaded the latest ICS leak onto my sd card, renamed it and put it in my phone. It started to load the file and showed me the 15 or so things that will be updated. I started the update and each of the 15 items said "Fail PU" except nfc. Its as if the partitions are just gone.
As you can see from the image, I have S-off, with unlocked boot loader. So now it appears that the battery doesn't charge on the bootloader screen. I left it plugged in all night in an attempt to charge the battery. I couldn't plug the phone in without it turning on and going right to the bootloader. So, I left it plugged in with the screen on all night and the battery is still dead. Now I can't start the phone to attempt anything further.
I've alreay called T-mobile to do a warranty exchange so there is a new phone on the way. Once I have it I should be albe to get a battery charged and into the old phone and try to restore it. I would like to get it back to factory with S-On with bootloader locked in the event that they decide they don't want to honor my warrany.
Any advice is welcome.
Thanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok so the image cuts off the S-off and hboot version, sorry.
You should lock your bootloader before flashing ics leak
Try flashing eng bootloader by naming it ph85img.zip and flashing in bootloader. That will give u a locked bootloader. Then try flashing ics ruu
All of this after getting a new battery of course.
_________________________
Am I on Candid Camera?
failed pu is full brick. You should check out the unbricking thread in the dev section.
Check it out http://forum.xda-developers.com/showthread.php?t=1627882
Thanks for the replies. I don't think that the unbrick tool supports my situation, but I will give it a try as I don't have much to lose. T-mobile is already sending a replacement so either way I should be ok. I have reverted to my trusty HD2 running ICS 4.04. Flashed probably over 100 ROMS onto the HD2 and never had a problem.
Just curious.
You said that ADB didn't recognize your phone. ADB only sees your phone when the phone is in recovery or fully booted up. When it is in bootloader, you can use fastboot as you have done trying to flash the ICS leak.
Did you try flashing the stock boot.img? The faux's kernel may not work as it is designed for GB. Well, I haven't tried it on my ICS so I'm not too sure.
Well, actually, you should try flashing things in the following order.
1. recovery.img from fastboot. If you can get it flashed successfully, at least you can adb shell into the system and see if your data is intact and nandroid back up to be safe.
2. kernel (boot.img) from fastboot.
3. some gb roms starting with something as close to stock GB as possible. Do it only if you can get recovery to work and flash only from the recovery, initially. RUU zips usually contains more stuff and if flashing fails, like in your ICS case, the system may go crazy.
I hope it helps.
well I got the replacement phone and charged the battery up. I put the battery into the old Amaze and it won't even turn on. It's completely dead. I guess I'm gonna just send it back. No hope for my data. Luckily have a backup from 4/28.
Thanks for the helps folks.
Slavid said:
well I got the replacement phone and charged the battery up. I put the battery into the old Amaze and it won't even turn on. It's completely dead. I guess I'm gonna just send it back. No hope for my data. Luckily have a backup from 4/28.
Thanks for the helps folks.
Click to expand...
Click to collapse
Hey, just wondering, sounds like even if you have rooted your phone and install custom ROM T-Mobile will still honor the warranty. Is that correct? I thought they won't if you have rooted your phone...
Slavid said:
well I got the replacement phone and charged the battery up. I put the battery into the old Amaze and it won't even turn on. It's completely dead. I guess I'm gonna just send it back. No hope for my data. Luckily have a backup from 4/28.
Thanks for the helps folks.
Click to expand...
Click to collapse
Hope you have a better luck with the new phone!
shuvarts said:
Hey, just wondering, sounds like even if you have rooted your phone and install custom ROM T-Mobile will still honor the warranty. Is that correct? I thought they won't if you have rooted your phone...
Click to expand...
Click to collapse
By reading many threads relating to unlocking/warranty, I am convinced that they will honor the warranty as long as the problem you are having is NOT related to the unlocking and subsequent modding of the device by you.
Well, sometimes it's hard to tell what happened if your phone is completely dead, though.
ringochan said:
Hope you have a better luck with the new phone!
By reading many threads relating to unlocking/warranty, I am convinced that they will honor the warranty as long as the problem you are having is NOT related to the unlocking and subsequent modding of the device by you.
Well, sometimes it's hard to tell what happened if your phone is completely dead, though.
Click to expand...
Click to collapse
Failed pu means the memory is shot. Nothing will write to the partitions. Warranty job
That's what I thought. The internal memory must have fried. I've had this happen to SD cards where suddenly they are blank. I imagine the same thing can happen with internal memory.
I already got my new phone and it's all restored, unlocked, s-off and running a custom rom.
thanks everyone.
Today I manually flashed 5.1.1 (the device have never been able to upgrade normally, "too low memory.. something") and all went good until I restarted. Now I get error msg "This is a development device not intended for production use", device is locked, I can't flash anything - "Permission denied".
It also seems as I have received a device not made for sale ?!!! I bought this via google store. Has this happened to anyone else ?
sigfrid56 said:
Today I manually flashed 5.1.1 (the device have never been able to upgrade normally, "too low memory.. something") and all went good until I restarted. Now I get error msg "This is a development device not intended for production use", device is locked, I can't flash anything - "Permission denied".
It also seems as I have received a device not made for sale ?!!! I bought this via google store. Has this happened to anyone else ?
Click to expand...
Click to collapse
See post #97 here > http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118/page10
cam30era said:
See post #97 here > http://forum.xda-developers.com/nexus-9/orig-development/root-t2929118/page10
Click to expand...
Click to collapse
If I try to flash a image I get errormsg: "Can not flash any image when device is locked!"
If I try "fastboot oem unlock" the msg is;
ability is 0
Permission denied for this command!
sigfrid56 said:
If I try to flash a image I get errormsg: "Can not flash any image when device is locked!"
If I try "fastboot oem unlock" the msg is;
ability is 0
Permission denied for this command!
Click to expand...
Click to collapse
Try this > fastboot format cache
Then > fastboot format userdata
Note that if this works it will totally wipe your device, including contents of SDcard.
cam30era said:
Try this > fastboot format cache
Then > fastboot format userdata
Note that if this works it will totally wipe your device, including contents of SDcard.
Click to expand...
Click to collapse
Tried it and it didn't help. Device is still locked. and unflashable.
I too am stuck in the same boat as you. I've tried multiple ways to flash/update including sideloading the signed OTA's via stock Recovery. At this point I just think it's RMA time to HTC
sigfrid56 said:
Tried it and it didn't help. Device is still locked. and unflashable.
Click to expand...
Click to collapse
You can try this. Look at post #57 > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
cam30era said:
You can try this. Look at post #57 > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
Click to expand...
Click to collapse
Tried that too, thank you. Didn't work.
sigfrid56 said:
Tried that too, thank you. Didn't work.
Click to expand...
Click to collapse
One last shot. Read post #56 here and try that > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
Try contacting Google, if you got it from them and it has the correct serial they should be able to help you with an exchange. at least, I hope.
cam30era said:
One last shot. Read post #56 here and try that > http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312/page6
Click to expand...
Click to collapse
Tried that too after looking at #57. Didn't work either. Now my tablet will go to the trashcan.
sigfrid56 said:
Tried that too after looking at #57. Didn't work either. Now my tablet will go to the trashcan.
Click to expand...
Click to collapse
Before you do that, I'd suggest contacting both Google and HTC. If that fails, it's still worth something on eBay.
same problem
UPDATE
Talked to Google and there is definetly no wy to fix it.
I am getting my N9 exchanged by amazon(since i bought it there)
Do not bother trying to fix it yourself - because there is now way.
Sorry for all of ya.
Same problem here. Installed the 5.1.1 update like always. getting this on boot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Contacted Google and they sent me a how-to to wipe cache and factory reset ...
Already tried some of the mentioned workarounds.
None of them worked, since my bootloader ist locked too.
Was hoping for fastboot oem verified -> fastboot wipe cache and userdata, but that did also not help...
I am on the brink of smashing this thing. How can Google screw up an official update like this?
I'll keep you updated for those who are having the same problem right now.
Worst OTA Ever !!!
Same problem, looks like Google really screwed this up!
I tried to unlock the device, but no way to do that from the bootloader, tried to wipe both cache and user data, still cannot unlock / flash ...:crying:
I've just had the same issue, trying to update just to 5.02 I'm getting a replacement from Google. I've never had this happen with one of their devices.
Error BUT OE ROM works/Loads 100%
hi all. I just bought a N9 (I do NOT want to root it) with this same error showing up at charge and when shut off/rebooting stage.
The N9 has factory ROM loaded
BUT the N9 still works 100%. Nothing seems to be wrong with my ROM and any feature I've played with seems to be working perfectly well.
So since I have no intentions of rooting/loading ROMS. I just want the factory ROMs from Google Updates, should this be something I worry about, or just ignore?
I got a smoking deal on this, the keyboard cover and another silicone case with magnetic cover so I really don't want to ask seller for refund.
I spoke with the seller, who is a computer science major about the issue and he profusely apologized and said he will take it back and fix the issue ( so he did this morning).
He rooted the device but never flashed any other ROMS. He just wanted the device rooted. So when he locked it again he figures that it what set off the "tampered flag"/error message.
So maybe since he never flashed another ROM to the device that has everything to do with why it still works 100% still, yet I'm getting the red letter message.
I spoke with HTC about this today and they said if the device is working fine and loading to the ROM no issues, then totally ignore this msg.
I just wanted to ask the seller to remove the error message if he can because if I decide I don't like the size of the device and I try to sell it I'm worried another buyer may be weary of the error message (as they should be really).
UPDATE:
OK, so this is my solution, according to the guy who fixed my N9
"So when you unlock the bootloader it actually allows any android device to be updated easier. So it can be updated either on the tablet directly or manually updated on the computer. Unlocking the bootloader isn't the same as rooting the device.
So I have actually unlocked the bootloader. I was actually running some tests, and the red text appeared because the program I used to factory restore the tablet and lock the bootloader wasn't official. So I took Google's original software for the Nexus 9 and put it on. So everything should work fine now, you will get regular software updates over the air and everything should be fine.
I have turned on and off the tablet 7 times now and there is no text when it is booting up or shutting down. Charging seems to work perfectly fine and it is able to connect to my computer."
maybe that will help others, maybe not.
UPDATE: Feb 11
So Google released a Feb security patch last night and my N9 can not install it. It downloads fine and tries to run but after 1 second of installation it fails and android is on his back with the word ERROR underneath. I am not sure if this ie becasue my factory ROM is re-installed BUT the bootloader is NOT locked again (left unlocked by the last owner). SO I downloaded Wugfresh's NRT and used the RELOCK button and after it wiped my tablet, now the red error "This is a development device not intended for production use" is back on my tablet again. ugh. I'll try using ADB and fastboot to bring back to factory spec. I do not need to have my tablet left in unlocked state as many of you may want. I just want a reliable N9 that updates the factory ROM and security patches OTA. I do not want to have to play with this.
I assume this is no longer an issue?
I had this message during an update to Nougat on a Nexus 9 that arrived that morning from Agros refurbs on Ebay.
I panicked and got here before the update completed but I needn't of worried Nougat went on with no issues at all.
I also got this message during the update to Nougat on a tablet I bought off of eBay. The update went fine and no longer displays that message during boot up. So, I guess it's OK.
SOLVED: Check the last comment.
---
So I have an Allview 3 Speed Quad HD or as I've found out on the internet this might be an Onda replica tablet (Chinese). Not really sure on what the exact model is.
The problem with this tablet is that the wi-fi was not working at all. I managed to root it.
Then I wanted to get TWRP on it. I found this thread/ and I tried the v2.6.0.0 for Onda V972 (SDK v3.2 base) TWRP. The ROM on it has an easy way of flashing from inside the system.
I boot it into rcovery but now it looks something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and like this if I press the Power button again:
I'm guessing it's clearly the wrong version. The buttons on the screen don't respond.
Any idea what I could do to fix it? I can't boot into the OS because it boots into TWRP everytime I open it.
I was doing all this to try and find another ROM that might fix it's wi-fi problem. Hoping it's not a hardware problem.
Here is more info on the tablet:
http://i.imgur.com/Fq3povk.jpg
http://i.imgur.com/nFN745q.jpg
http://i.imgur.com/8G7opVx.jpg
http://i.imgur.com/ZUn7o6z.jpg
(these were taken before)
I would appreciate any help.
Thank you
If there any other versions of TWRP for A31 of its yours CPU, you can try out.
And also you can try Kingo Root in order to root.
In order to flash stock ROMS you don't need TWRP.
Some ROMS can be flashed via USB and dedicated software.
deton24 said:
If there any other versions of TWRP for A31 of its yours CPU, you can try out.
And also you can try Kingo Root in order to root.
In order to flash stock ROMS you don't need TWRP.
Some ROMS can be flashed via USB and dedicated software.
Click to expand...
Click to collapse
Yes, but right now I am stuck. I can't boot into system. It will automatically bring me into the broken TWRP.
Any idea how I can unstuck myself?
Download stock ROM for your tablet from the manufacturer's page and flash it via USB with dedicated tool/other method which will replace recovery partition too
deton24 said:
Download stock ROM for your tablet from the manufacturer's page and flash it via USB with dedicated tool/other method which will replace recovery partition too
Click to expand...
Click to collapse
Hey, sorry for bothering you again.
I didn't find the stock ROM anywhere. All the links to them are dead because they're from 2013.
I tried other ROMs from Arctablet, specifically from here. I tried the v972 and v975 ROMs because I honestly can't tell which model is mine.
I did this through the PhoenixSuit tool, but after it finished upgrading the firmware the tablet doesn't boot. I can see it light up, but it just sits there with a black screen.
Any idea what it is? Is it completely bricked at this point?
I'm not sure how to use adb in this case. The tablet is still being caught by the PC and the PhoenixSuite sees it, so I can still try other ROMs. But I feel like I should try with adb.
Can I do anything?
Mail manufaturer for stock ROM files.
You've searched on their site?
You can also try TWRP from here
http://www.slatedroid.com/topic/63602-recovery-twrp-2600/
Maybe any package will start working, but as you see, there are packages for specific models
If any of links are dead, send PM to the author.
On full version of the site (button on very bottom if on mobile) you have his signature linking for few of his versions of A31 ROMs on different devices.
Checked yesterday this a bit. There is one Romanian forum in which this and onda firmware was discussed.
https://forum.softpedia.com/topic/921738-allview-alldro-3-speed-quad/page__st__54#entry14909043
Two stock firmwares were mentioned for it. But is yours it? Oddly your screen resolution is smaller.
http://web.archive.org/web/20131008...-tablete-pc/alldro-3-speed-quad/specificatii/
Download links for those stock firmwares.
http://web.archive.org/web/*/http://www.allview.ro/fileadmin/update/Update_3SpeedQuad_19.06.2013.rar
http://www.fileshare.ro/e31842897
First dl link from these two above from archive org downloadable here
http://web.archive.org/web/20131011...admin/update/Update_3SpeedQuad_19.06.2013.rar
Nice work
CXZa said:
Checked yesterday this a bit. There is one Romanian forum in which this and onda firmware was discussed.
https://forum.softpedia.com/topic/921738-allview-alldro-3-speed-quad/page__st__54#entry14909043
Two stock firmwares were mentioned for it. But is yours it? Oddly your screen resolution is smaller.
http://web.archive.org/web/20131008...-tablete-pc/alldro-3-speed-quad/specificatii/
Download links for those stock firmwares.
http://web.archive.org/web/*/http://www.allview.ro/fileadmin/update/Update_3SpeedQuad_19.06.2013.rar
http://www.fileshare.ro/e31842897
Click to expand...
Click to collapse
Much appreciated! Your Google-fu is way better than mine.
I'll try that ROM and see how it goes.
So I flashed that ROM (Update_3SpeedQuad_11.09.2013) with PhoenixSuite. All went well, it said Firmware upgrade successful. It even opened up by itself at the end, something that it wasn't doing with the previous ROMs, but it just stays like that. Black screen, but you can tell it's opened. It also actually quickly closes and opens up, which reminds me of the moment it would switch to the boot animation. I left it like that for 10 minutes, thinking it might be a long boot with no boot animation.
Any idea what it could be? Did I completely mess it up with that TWRP? Is there anything else I could try?
There seems to be a third batch or version of those - at least.
http://www.slatedroid.com/topic/73537-onda-replica-need-help/?p=1202409
The firmware Vadwiser mentions?
http://www.arctablet.com/blog/forum...-bean-root-custom-firmware-v3-3-1-2013-11-22/
Getting correct firmware from the vendor would be the best. Or a dump from someone.
If not possible then getting correct modules from some stock(s) mentioned... with luck.
Solved
Ok, I finally got it to work. (although, wi-fi still doesn't work )
Allview 3 Speed Quad HD is Onda v975s (I tried V975s Core4_V3.3.2_v1.img and it was the first one that actually worked)
I downloaded it from this website (the official Onda forum) and there are a lot more ROMs there, which I'll start testing.
I tried kasty-onda_v975_v1-422-v332_20131227-rooted0.zip from the arctablet forum, but it didn't work. So clearly v975 is quite different from v975s.
Now I'll just try all the original Onda firmwares, because I can't really find a Custom one for the v975s. Maybe I'll find a way to root it at least.
I honestly should've researched better the specifications. The resolution of this tablet is 1024*768, but I never thought this is so essential. So I never checked the other models properly to see if they fit better. And honestly they still don't completely fit, because on this website (where I initially noticed the resolution) it says 16 GB storage. And mine has 4 GB.
Allview probably changed the storage before they started selling it in Romania.
Thank you CXZa and deton24 for helping out!
Hi everyone, thanks for reading. I'm completely new to this so please bear with me if you can.
I got a very cheap unlocked Huawei Mate 10 pro as a gift about 2 weeks ago. It's 64gb, dual sim.
I've tried to set it up many times but it glitches very fast, every time.
If I try to download any apps I get a 192 error code after 4 apps, or a "not enough memory" warning, even though the phone is completely empty. It also happened the one time I managed to install whatsapp and load the back up files, it kept asking to free space but there was nothing else in it.
Erasing the apps and download cache only works a few times before every single app crashes, including Play Store, over and over again. The only app that doesn't crash is Settings. I've done reset after reset to the same results.
I even tried entering the recovery menu but I got the "No Command" screen.
I've kept investigating and found this forum, I want to try flashing the ROM and/or rooting, I think there's no other solution, but reading the guides and looking for the info requested from my phone made me realize that this phone is a clone. For example on About phone>model number it just says "mate 10 Pro" instead of a regular model number. I googled the Custom build version (ALPS.L1.MP6.V2) and got a lot of videos about clone huawei phones.
So my question is, can anyone please help me understand and fix this phone? Is it doable?
Here is a screenshot of the About phone menu, if you are interested.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its probably a mediatek chipset. Don't try to flash it with roms for huawei. Problem is that you have to find out which one you have... There are many clones. Prices varies from 90-100 dollars... ? So a lot of times very poor specs. Also no support for the software. Good luck with this
wooley4766 said:
Its probably a mediatek chipset. Don't try to flash it with roms for huawei. Problem is that you have to find out which one you have... There are many clones. Prices varies from 90-100 dollars... So a lot of times very poor specs. Also no support for the software. Good luck with this
Click to expand...
Click to collapse
Yes, it was very cheap but not even worth that, tbh. I'd still like to use it though, it was a gift and I feel bad for the person who got it for me. Any ideas where I can look to see which one I have?
Thank you so much for replying, I'll continue my research
viela said:
Yes, it was very cheap but not even worth that, tbh. I'd still like to use it though, it was a gift and I feel bad for the person who got it for me. Any ideas where I can look to see which one I have?
Thank you so much for replying, I'll continue my research
Click to expand...
Click to collapse
Hm,can you try to find out the specs of the phone and what clone it is,since on MediaTek phones I believe ROM porting is pretty easy if you know what chipset it is.
Because if you can manage to port a clean ROM of some version of Android then you can greatly enhance the speed and performance.
viela said:
Hi everyone, thanks for reading. I'm completely new to this so please bear with me if you can.
I got a very cheap unlocked Huawei Mate 10 pro as a gift about 2 weeks ago. It's 64gb, dual sim.
I've tried to set it up many times but it glitches very fast, every time.
If I try to download any apps I get a 192 error code after 4 apps, or a "not enough memory" warning, even though the phone is completely empty. It also happened the one time I managed to install whatsapp and load the back up files, it kept asking to free space but there was nothing else in it.
Erasing the apps and download cache only works a few times before every single app crashes, including Play Store, over and over again. The only app that doesn't crash is Settings. I've done reset after reset to the same results.
I even tried entering the recovery menu but I got the "No Command" screen.
I've kept investigating and found this forum, I want to try flashing the ROM and/or rooting, I think there's no other solution, but reading the guides and looking for the info requested from my phone made me realize that this phone is a clone. For example on About phone>model number it just says "mate 10 Pro" instead of a regular model number. I googled the Custom build version (ALPS.L1.MP6.V2) and got a lot of videos about clone huawei phones.
So my question is, can anyone please help me understand and fix this phone? Is it doable?
Here is a screenshot of the About phone menu, if you are interested.
Click to expand...
Click to collapse
I would check if you even have access to fastboot to flash anything/unlock it. Unless its unlocked already?
dinoderda said:
Hm,can you try to find out the specs of the phone and what clone it is,since on MediaTek phones I believe ROM porting is pretty easy if you know what chipset it is.
Because if you can manage to port a clean ROM of some version of Android then you can greatly enhance the speed and performance.
Click to expand...
Click to collapse
I found that on About phone> Legal Information> Open source licenses there is a "Notices for file(s)" list that mentions /system/etc/firmware/mt6580/mt6580_fm_v1_coeff.bin, it has lines like this for v1 to v5.
I'm not sure what that is but I guess it means I have the MT6580 since there is no other similar information in there, nor another menu that has any other info.
ante0 said:
I would check if you even have access to fastboot to flash anything/unlock it. Unless its unlocked already?
Click to expand...
Click to collapse
Yes, I tried a trick I saw on youtube and I was able to access fastboot. The phone is unlocked, meaning that you can use a sim card from any company. (That's what you mean, right?)
viela said:
Yes, I tried a trick I saw on youtube and I was able to access fastboot. The phone is unlocked, meaning that you can use a sim card from any company. (That's what you mean, right?)
Click to expand...
Click to collapse
He asked if the bootloader is unlocked,and on almost any MTK phone (excluding some from major brands like Sony) the bootloader is unlocked.
But that chipset is actually very very slow and I don't think you will be able to do anything about it.
Yeah if it's a 6580 there are roms for it, Good luck with this one https://youtu.be/EI10kCBTNi4
wooley4766 said:
Yeah if it's a 6580 there are roms for it, Good luck with this one https://youtu.be/EI10kCBTNi4
Click to expand...
Click to collapse
Thank you so much! I'll give it a try and report back, maybe the thread will help other people like me.
I have encountered this problem too. any luck on finding a flashable rom? I have downloaded some but it's asking for a password.
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
Give me some time working on it , u have spent so much time on this , can u spend little more . I may help u so let me do some research and come to u
DIVASM said:
Give me some time working on it , u have spent so much time on this , can u spend little more . I may help u so let me do some research and come to u
Click to expand...
Click to collapse
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy
Click to expand...
Click to collapse
stop_making_things_worse said:
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
can u try this
, if it is not wokring tell me
That is one of many videos and posts I have already seen and followed. The fundamental issue is not being able to unlock the bootloader in developer options. No amount of dancing gets "OEM Unlock" to display for me. Other threads indicate the 227U specifically does not have a way to unlock the bootloader, while 225/227 do.
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make Self Root And Try
I have same frustration nothing is getting the oem to show up. I have some know how's with rooting ect my other tablet is my Frankenstein lol but unfortunately it's not one of these tabs. Any word on a fix ?
wesmat95 said:
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
View attachment 5936903
Click to expand...
Click to collapse
Hm interesting, if you boot to download mode, are you able to unlock the bootloader there?
wesmat95 said:
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
Click to expand...
Click to collapse
This is a very interesting piece of information. I believe we can flash official firmware from samfw without worry, so I will try this route, however this specific build isn't available that I can see (it's old, they only have newest I guess?). I'll try the version they have and cross my fingers that it works and my SIM still works.
You did not have to do any steps, correct? OEM Unlock option showed without having to do the whole date/time dance?
stop_making_things_worse said:
This is a very interesting piece of information. I believe we can flash official firmware from samfw without worry, so I will try this route, however this specific build isn't available that I can see (it's old, they only have newest I guess?). I'll try the version they have and cross my fingers that it works and my SIM still works.
You did not have to do any steps, correct? OEM Unlock option showed without having to do the whole date/time dance?
Click to expand...
Click to collapse
No I did not. It just appeared in developer options. I just got this tablet about 7 months ago. Just got it out to do some development on it. I do have to mention that it is on the latest One UI update that appeared on my device a couple days ago. I did however notice that there are newer updates on SAMFW for it not available on my device. Maybe Rogers blocking update? Don't know. Found it wierd.
Wish39 said:
Hm interesting, if you boot to download mode, are you able to unlock the bootloader there?
Click to expand...
Click to collapse
Technically I should be able to. Haven't done it yet though.
Having the same problem. Everything I've tried so far can't even get to the OEM unlock to appear in debug. Pretty much hobbles doing anything. Is the freebie SM-T227U with android 13. Box has date of 05/09/23 so really new. Hardware revision 1.0 and SW is T227USQU4CWC2. Maybe a way to force flash older firmware and make OEM unlock work?
stop_making_things_worse said:
Other threads indicate the 227U specifically does not have a way to unlock the bootloader, while 225/227 do.
Click to expand...
Click to collapse
Really going to piss me off if true.
popeye2014 said:
Having the same problem. Everything I've tried so far can't even get to the OEM unlock to appear in debug. Pretty much hobbles doing anything. Is the freebie SM-T227U with android 13. Box has date of 05/09/23 so really new. Hardware revision 1.0 and SW is T227USQU4CWC2. Maybe a way to force flash older firmware and make OEM unlock work?
Click to expand...
Click to collapse
You could try flashing the Canadian T227U firmware using patched Odin, as it apparently can be bootloader unlocked.
We have AT&T and Verizon to thank for making Samsung permalock the devices they sell in the US.
Wish39 said:
You could try flashing the Canadian T227U firmware using patched Odin, as it apparently can be bootloader unlocked.
We have AT&T and Verizon to thank for making Samsung permalock the devices they sell in the US.
Click to expand...
Click to collapse
Thanks probably will try something like that. At this point might as well try even if end up bricking it. Really want it unlocked and the ability to use other carriers. Last thing I need is another tablet with just wifi. which is what it pretty much is being locked.
wesmat95 said:
Technically I should be able to. Haven't done it yet though.
Click to expand...
Click to collapse
I can't even get to bootloader. When it inters fastboot it just says interning fast boot and never actually does. I have no idea why
bencinilife said:
I can't even get to bootloader. When it inters fastboot it just says interning fast boot and never actually does. I have no idea why
Click to expand...
Click to collapse
Fastboot doesn't exist on Samsungs. They replace it with Download mode
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
I am literally going threw the same thing! i see everyone with different variants of the a7 lite doing this all day. I've tried everything to get the OEM Unlock option to pop up and literally nothing! Never ever thought it would just not be possible out the gate. Ive got the T227USQS5CWD1
Hardxcore_Cary said:
Never ever thought it would just not be possible out the gate.
Click to expand...
Click to collapse
Then you must not have purchased or used any North American Samsung devices in the past 5+ years.
Another user with a Canadian model reported having OEM Unlock (although I don't believe they've clarified whether they could actually do the BL unlock via Download mode).
So you could try flashing Canadian firmware
Update trying to flash Canadian FW to US (TMOBILE) tab:
Pulled both major versions up on samfw and tried differnet things. As a preface to outlining the issues I am facing, I have to state two things: 1) I have no idea what these files actually are. but 2) If I flash BL+AP+CP+CSC files that are for my carrier, it works fine (I've had to unbrick this by doing this several times). So, I can and have successfully flashed what is basically already the official FW for my device (SM-T227U_TMB_T227USQS5CWD1_fac <---this succeeds in ODIN).
I have now tried SM-T227U_RWC_T227UVLS5DWC5 and SM-T227U_RWC_T227UVLU4DWC2. I get different errors based on how I go about it, but errors nonetheless.
If I just blanket try BL+AP+CP+CSC I get
Code:
Non-KNL image not allowed: pit
If I use the BL+CP+CSC from my carrier and only the AP from RWC (I assume this is rogers), I get
Code:
Non-KNL Image not allowed: boot
For T227U_RWC_T227UVLU4DWC2 there's an additional error message of
Code:
Fused 5 > Binary 4.
RP Check Error: boot
Non-KNL Image not allowed: boot
I assume this is because the fw version doesn't match the "fused" version or something? I dunno.
Just reporting my findings.
EDIT: Upon further inspection of all the FW offerings, it appears only T227UVLS5DWC5 (Canada), T227USQS5CWD1 (US), and T227USQU5CWD2 (US) are even remotely viable due to device requiring U>=5 (sw/ver, bin value, whatever you want to call it). Unless there's a way around this?
I have validated that I can flash BOTH US F/Ws successfully, even though one is for a different carrier in the US. But the canadian version is a no-go due to the pit/boot errors noted above.