Have a Meep tablet. It starts up then when trying to load software its stuck in endless loop. I want to update, but don't know how to get into recovery mode. Tried adb, but device not recognized. PC sees it as mass storage. If debug not enabled, anyway to get access to file system?
No Recovery
Unfortunately, to the best of my knowledge, there is no recovery mode for the Meep. Even with USB debugging enabled, adb reboot recovery does not work. It will just reboot the Meep and nothing else. If you take the Meep apart, there is a very small switch behind the headphone jack, if I remember correctly. It was a bit difficult to reach. If you push that button in, while sliding and holding the power switch to the right, it will allow you to boot in a type of recovery mode. However, all options are in Chinese, I believe. I ended up breaking the power switch. I would not recommend doing that, unless you know what you are doing, which I didn't completely. If your Meep is still under warranty, (one year, if purchased in the US, possibly two if purchased in Europe), I'd recommend contacting their call center at 1-800-853-8883. Press option 7, once connected. They are open Monday thru Friday, from 8am to 5pm, Pacific Standard Time. They are closed on most major holidays. Typically, for the issue you are having, they would consider it a hardware issue and have you mail in your old Meep. They should give you a RMA number. You may have to pay return postage. In return, once received, they will ship you a new Meep. For Europe, I have seen posts from the France and Italy facebook Meep pages, telling people to return the Meep to the place of purchase. The store should be able to coordinate a return of your Meep, under warranty, to the factory. In return, a new Meep should be mailed to your address. I have heard it taking up to several weeks to get the new mailed. That's the best advice I can give. On another note, someone posted a custom ROM on the Phandroid web site. The ROM was made from the LY-F1 image file for Allwinner A10 devices. The Meep uses an Allwinner A10 chip. Links to the image file, Livesuit (sic), and instructions are located there. Livesuit is used to flash images on Allwinner A10 devices. As your Meep is stuck in a bootloop, so to speak, I don't know if flashing that image will work. Also noted with that image, the camera may not work. I has worked for some, but not for others. Good luck!
Related
So I have a bad feeling here. I was fixing my ad hoc problem and accidentally renamed my /system/bin folder to "bin - Copy" not sure how I did it, a finger swype n boom it was that way. Could not change it back. Rebooted and now I can't get passed the Eee Pad boot screen. Any one know how to fix this?
I've got a similar problem.
There should be a sollution where you start up, holding the powerbutton and volume up. You feel a vibrate and the screen stays black.
with this way you can connect your transformer, and access it. But I don't know how.
Windows reconiges the device as and APX (under linux as an Nvidia device) But I can't connect to it, don't have the drivers and so.
So is anyone knows how to access the prime trough this method, our problem could be solved using adb pulling and pushing these folders.
Greets
If you connect it to your computer can adb access it??
Nope. Going to try a couple more things this evening.
Sent from my PC36100 using XDA App
Well, I tried a bunch of different things: microsd recovery, wipe data, recovery, "up volume/pwr button", broke down n called Asus. So here's what happened in case anyone else comes across this thread: microsd method to flash firmware=nothing, anytime I entered recovery Andy laid down and opened his chest cavity and red triangle !, wipe data done. signature match=freeze up at that screen, no reboot. hard reset with paper clip=nada just reset to frozen eee pad screen. I have linux 11.10 and 10.04BT on another hdd so I booted to both b/c I read a post somewhere about booting the prime by holding up volume/pwr and its supposed to be some kind of nvidia diagnostic mode. Interestingly in windows it changed from an unknown MTP usb to APX device doing this, in Linux it never even came up either way. I don't know enough about this, so I tried searching and reading=nothing fruitful. I'm a Linux and ADB noob so I read and read and read some more, but after trying a few walk throughs, my Prime just seems to be dead. So I called Asus and played dumb, said it froze after trying to update to ICS. He walked me through these other steps I mentioned to no avail. Then he gave me an RMA# so I went ahead and mentioned the excessive light bleed and non-functioning GPS. He noted those issues and now I'm sending it in apparently. I was REALLY hoping to avoid this b/c this was my fault, but my experience with the Prime has prompted me to ad my 2 cents/rant in the general thread.
I wish this had a better outcome, but with the bootloader locked I and many others have been unnecessarily doomed to RMA.
Well that sucks big time... hope you get another soon
hoping to hear about an update to this other than sending it in. unfortunatley i have just done the exact same thing.
There are APX drivers in the dev section. My Prime changed from APX device to Asus Transformer prime APX mode when I installed them. After that I don't know what to do; I think we need an nvflash for the Prime or something.
Mine went into APX mode after the last OTA update failed and won't leave APX mode for anything, so I was looking for a way to connect to it to flash an update or something, but no luck so far. Maybe Asus will release a tool for us to fix a failed OTA update, would be a lot better than sending my tablet away for a month so they can do it.
I searched and searched for this too. Couldn't get anything to work.
As for an update, as of about a couple hours ago, looks like they are sending me a new tablet. Has a different serial number listed as "ready to ship" and states "original serial number: C1O....." which is the s/n of the tab I sent in.
So we'll see if this one comes with no light bleed and working gps. Don't think I'll be screwing this one up! Gonna be extra careful...
I was in the same situation, stuck. I tried everything you did as well and nothing. "Doktaphex" gave me this link http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119 in my post and it worked perfectly. I was sooo damn happy to see Andy actually working instead of laying down when I entered RCK
Oops...shoulda read through. Hehe sorry bout that :/
That would've been just one more thing to try on top of all the other things I tried. If it actually works, then ALL the other ppl that say to use this microsd recovery method need to read your link and actually know what they are talking about. I read method after method and tried them all to no avail.
I did this and that worked for me : http://forum.xda-developers.com/showpost.php?p=22857274&postcount=21
Got my replacement Prime today. Putting it through the paces now. GPS isn't noted on the box, but I don't remember if it was on my first one. Still a C1O serial. Went ahead and updated first, bc I don't care about HC.
GPS: Can see 4 but signal stays under 35, no locks. will try again tom from Dallas
BT/Wifi issue: None, Does not degrade
Wifi range: Not bad, little better than my phone
Light bleed: Better than last, but still 5 spots along bottom and right side
Side Note: put a 64gb microsd in the tab and a 64gb microsd w adapter in dock. Both work fine, now up to 192gb.
I'm very happy Asus replaced this so quick (week and 1 day). I'm not a picky person so I am fine w the lesser light bleed, I will never use gps but it would be nice to have as an option. I bricked my first tab and would gladly have paid for them to reflash it, heck if they called me even now and said, "hey, we found that you bricked your own tab, here's a bill to reflash" I'd gladly pay it. So far I have to agree w everybody's sides to every issue, which is crazy to think, but everyone has legitimate points. Except ppl that expect Asus to still warrant after unlocking n flashing roms, that's ridiculous.
Just a background:
This is not my device
This is a stock OS/nonrooted device
I have done some development on Android, so am somewhat experienced
I am helping a friend who just wants it to work again
Kindle Fire HDX 7" model # C9R6QM
What's going on:
Device is stuck on light gray "kindle fire" boot logo.
Device is not showing in device manager on Windows 7 PRO
Device is not showing in adb "adb devices command"
Device seems charged, has been left with cord in for longer than several hours
Tried several different cords to rule out faulty equipment
Tried multiple USB ports including 2.0, 3.0, front and rear ports, even a powered USB hub
Tried hard reset multiple times using power button
Tried power and vol up to go into a recovery, nothing happens.
"fastboot devices" command shows only "waiting for devices"
Help! I just need to get this thing up and running again, no matter the cost to data. Only thing I haven't tried is the bootloop utilities yet, as I am on a work pc and do not have access to download them atm. Will try these later if I need to.
Thanks in advance, and ask any questions if you need more info.
-Tripp
UPDATE 1: Upon further playing with device, I have finally gained access to the "Fire System Recovery" page seen here.
Well I guess since I am a new user still I cannot post the photo, but it is kindlefire recover page with a bunch of E: failed and E:cant mount stuff underneath. If I need to spell it all out I will.
Unfortunatly, neither "reboot your kindle" or "reset to factory defaults" does any good for me. Rebooting just causes it to bootlogo screen again, and Reset to FD fails, getting some weird oldschool tv effect on the screen until it reboots again into recovery and gives me the same two options.
ADB, windows, and fastboot still do not detect the device while in recovery.
Any ideas?
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
EncryptedCurse said:
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
Click to expand...
Click to collapse
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
trippvail said:
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
Click to expand...
Click to collapse
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Davey126 said:
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Click to expand...
Click to collapse
Damn was hoping there was a fix. I am sure that adb was never enabled as they are not tech savvy. Nothing shows in device manager when it is plugged in, ever. No changes.
Update 2:
So I popped in my Ubuntu drive and booted up. After installing adb and fastboot just in case, I tried accessing the kindle in both boot logo and recovery modes. No luck.
Ubuntu doesn't even see it there...
I know I'm not going crazy but it seems like I'm missing something somewhere. I have been through multiple brickings of our developer phones and brought them back to life but they always had adb enabled. Seems like there has to be a work around.
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
trippvail said:
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
Click to expand...
Click to collapse
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Davey126 said:
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Click to expand...
Click to collapse
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
trippvail said:
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
Click to expand...
Click to collapse
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Davey126 said:
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Click to expand...
Click to collapse
Ya I can understand that. I'm actually using an iPhone right now, jailbroken of course lol. But I understand why Amazon did it. Too bad a tablet has to die because of it though. I love the open Android systems but I like apples hardware better. Haven't found an android phone I like better yet. To each his own, right?
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
draxie said:
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
Click to expand...
Click to collapse
I don't and neither does the owner. I would assume the latest if it auto updates, although that may be what bricked it if it didn't have the power to complete the update. Can't confirm any of that though.
I will try both volume buttons in a bit when I get off work. I did the vol up with power to get into recovery, but that did nothing for me as recovery failed every time and rebooting just takes me back to the gray kf logo.
Ok so I tried the vol up and down while powering it on and it just took me to recovery. Same E:failed to mount and E:can't mount/can't open messages below the recovery options in yellow. So I guess I'm screwed then.
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
draxie said:
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
Click to expand...
Click to collapse
I will be trying your methods draxie when I get home and back with the device today if what I am doing now doesn't work. I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
At this point recovering anything from the device is nothing to me, or the owner, as there was nothing important on it. I was hoping to not take the hardware route, but I have the tools, the time, and the hands to do it if necessary. All I need is the knowledge from someone as to what the hell I'm looking for in there.
Just to confirm, after the gray logo of KindleFire comes up, should I be seeing anything else come up while holding buttons for fastboot? <<Just re-read your post and realized it answered this question>>These things are so much easier to use when rooted and TWRP or CWM recoveries are installed. Android makers all over should take note and use the knowledge of the open source community to improve their own devices.
Below is a photo of the recovery screen I see now that I can finally post photos.
{
"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"
}
trippvail said:
I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
Click to expand...
Click to collapse
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
draxie said:
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
Click to expand...
Click to collapse
Lol thanks. I am sure it will be dead for awhile before I get home, if it's not dead already. But if for some reason it's still alive I will make sure to let it sit for an extra 30 minutes after it goes down.
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
jwcdis said:
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
Click to expand...
Click to collapse
If the bootloader remains locked with no access via tether (or wireless ADB) you are pretty much done. You can attempt the cold start remedy suggested in earlier posts. Long shot at best. Note the device should sit idle for several days after appearing to be depleted as internal circuitry prevents the battery from going completely dead. Even then some charge will remain which is necessary to respond to the power button and protect the battery from permanent damage. Removable primary and backup batteries are the only surefire way to insure a true cold start.
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Don Karnage said:
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Click to expand...
Click to collapse
Sorry for your troubles. Fastboot (aka factory) cables are useless on an HDX. If you can't 'see' your device via a standard usb cable or it shows up as "QHSUSB_BULK" then you're done. If the device was purchased within the past 12 months there is a good chance Amazon will exchange it for a refurb. Just say it died during an update (apparently true). No need to mention the prior root attempt which may or may not be related. Call and be nice to the rep; ultimately it's their decision.
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Don Karnage said:
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Click to expand...
Click to collapse
Those are encouraging signs. Do you recall enabling adb? If so there may be a way to revive your device via tether but the the commands/techniques are a little beyond me (others can probably help). Most require root access which you likely don't have. Best guess is the root exploit you tried was partially successful and may have altered some files needed to process ota updates. A factory reset emulates portions of that process likely resulting in the boot loop. If the offending 'update' file(s) can be renamed you might be able to boot successfully.
Don have you ever used ADB? If so this might possibly save you
http://forum.xda-developers.com/kindle-fire-hdx/general/unbrick-solutions-t3059733
Hi everybody,
a few days ago I received my brand new Redmi Note 2 32GB from gearbest. I spent a lot of time finding a suitable priced model from within Europe below EUR 200,-. Finally I managed from gearbest UK warehouse and looked forward to it.
First bad news was the price difference between the EUR amount shown on gearbest shop site and what paypal finally charged when fetching the money using their exchange rate to USD. So the phone was already much more expensive than expected but still below EUR 200,-.
Now I received the phone and switched it on without changing anything: First thing reboot loop with mi.com logog. Websearches result in the information that this only happened after some kind of rooting, flashing, etc. Neither of them I did.
After a while I managed to boot into android (this only succeeded 3 times within the past 2 days!). I could change some settings but then the screen did not react any more to any input. Neither did the keys below the screen - only hardware keys are reacting.
So I forced the phone to reboot only to get stuck in the reboot loop again. This is now ongoing and ongoing - I am stuck between reboot loop and non-reacting phone with some occassional seconds in between where I can use it.
As said: This is a brand new phone directly unboxed - nothing installed, nothing downloaded, nothing rooted, nothing flashed!
gearbest just offers either return on my own costs (which finally raises the price of this phone above a level where I could easily by it from some domestic shop) or they offer some ridiculous refunds but I can keep the phone.
So question is: Is there anything I can do here to get the phone working again without rooting/reflashing (using some kind of GSM codes or similar - the tip from here does not work for me. No menu occurs.
2nd question: Rooting and flashing different firmware will void my warranty anyway. But is there any chance that flashing a different firmware would even help in this cases (if not and it is a hardware problem I cannot sent back the phone for repair)?
I am really annoyed and frustrated!
Any help is highly appreciated!
Bye
Clearly, someone has flashed something that went wrong before dispatching the phone to you, and/or the device is faulty. At the very least, the device is not fit for purpose. You should take the issue up with paypal. I wouldn't recommend flashing anything, because then it will all be your fault.
DarthJabba9 said:
Clearly, someone has flashed something that went wrong before dispatching the phone to you, and/or the device is faulty. At the very least, the device is not fit for purpose. You should take the issue up with paypal. I wouldn't recommend flashing anything, because then it will all be your fault.
Click to expand...
Click to collapse
Since it came from a shop with the mentioned poor return possibilities I assume there is nothing PayPal can do against. I just wanted to check out my possibilities before returning the item (making it more expensive again).
Ok. Clearly, if it's a hardware fault, then flashing something new will not solve the problem. But how do you tell? I don't see any other way than flashing a new ROM.
Also don't see any way. Thought there might be some apps for analysing or something like the screen calibration where I posted the link (example given in that link does not work for me)?
Alternative would be: Returning the phone.
Are you able to enter recovery, and does it work correctly while in recovery?
If you can, you should try another rom from this forum. Maybe GearBest screwed up when they switched the original chinese MIUI to their "international version with bloatware".
If you can't enter recovery, you should return the phone.
To my knowledge there is no recovery installed. As said I just unboxed the new phone and tried to use it. The only thing I can enter is the fastboot screen.
Ok, found recovery mode. Inside is also one menu entry shown regarding installation of update.zip. But if I install a new ROM and it turns out to be a hardware bug - how to restore previous ROM in order to return the phone?
Also maybe important: Currently installed is MIUI-Version: MIUI 7 by xiaomi.eu 5.10.16 | Beta
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
No adb access? That sucks, as it should be pretty easy to fix if you could adb push. Were it mine, I'd go ahead and try to replace the screen on the functioning tablet. Not what you want to hear, but I think that's the only way to get working again. Best of luck.
Valence1981 said:
Last year I got annoyed that the Wishlist icon was repopulating itself to my Favorites every time I deleted it, so I got a wild hair to root my Kindle and take care of that junk for good. I did this before reading the numerous warnings about how this was an awful device to root on a whim. I proceeded to delete a bunch of system files related to Amazon ads and tracking. After a reboot, I found myself stuck at a flashing white Favorites screen. I could get to the Settings menus, but most choices didn't work and just took me back to Settings without changing anything. I couldn't connect to a wifi network, but I could see the networks, click on Connect to Network, and then it just took me back to Settings. I couldn't change any of the Developer settings. I did hard resets from that mode and from the boot up recovery menu. Nothing could get me out of this state.
Anyway, I posted thread about this when it happened, here: http://forum.xda-developers.com/kin...iles-flashing-favorites-screen-t3116682/page1
In the end, I didn't have the heart to scam Amazon, so I just bought a used HDX 7 and put the bricked one in the drawer in hopes of a future fix. Last night, my replacement Kindle's screen was crushed by some mysterious force, possibly a kitty cat or an adjustable bed. Though it's tempting to think about trying to swap the screens, I don't want to crack the screen and wind up with two broken displays (plus a bricked Kindle). So I thought I'd check back and see if there were any developments on the fixing-dumb-newbie-mistakes front for the bricked one.
The device does not show up in Windows XP, 7, or 8.1. The Kindle itself recognizes it's charging. As I mentioned in the old thread, I tried a Fastboot cable, but that apparently doesn't work on this model. So any hope? It's so frustrating because it seems like if I could just get the wifi to work I could download the latest OS update and it would fix this.
I understand if there still are no fixes for this. It was a dumb move to tinker with this in the first place. I was just hopeful something might have changed, since last I asked about it.
Click to expand...
Click to collapse
You're done if device is running 4.5.2 w/no adb access. There are a few last resort unbrick methods/tools but they are geared toward older versions of FireOS (v3.2.6 and below). Replacing the screen on a 7" HDX is difficult; copious use of glue makes for a tough job. Might check auction sites; prices are pretty low for 16GB models. Also consider the latest 7" tab from Amazon (2015 Fire). Specs are awful vs HDX but it really isn't that bad, especially for video and with apps designed for lower resolution screens (many are). Fully rootable with option for custom roms. FireOS v5 is a nice step up from v4, faster and more 'android like' (although still heavily skinned).