[Q] Pioneer R1 Tablet not rooted and wont load past the animated logo - General Questions and Answers

Hello,
My Pioneer R1 tablet the other night decided to do an automatic upgrade when booting up and hung for hours on 14 of 18 files updated. I rebooted the tablet for it to get to the home screen but come up with the error android phone services not initinalized and then froze. so rebooted and it got to the animated pioneer logo and just sits there never loading fully. Pioneer customer support sucks with helping and the tablet has a reset button on the back in a pin hole. I pressed that the tablet turns off. The tablet still stuck on animated logo.The tablet was running stock jellybean 4.2. The Pioneer people didnt want to do any troubleshooting. told me to send it to them to fix and that if they found anything wrong other than hardware issue i am liable for the charges on to of the shipping cost. I dont have money to just hand out to people who dont have a system setup for troubleshooting. Sorry for a long story but my question is is there anyone who can help me fix this issue.

Unfortunately I'm stuck with the same issue, tablet was running slow so I rebooted it, got hit with their "system breaking update"
Spent a better part of the day trying to find a way to reboot it into recovery mode and wipe user data/reinstall but so far no luck.
Fired off a email to support, tried calling but the wait time was 54mins last time I called.
Also there is a automated announcement while waiting for call time informing everyone that they "are aware of a problem with the tablet"
If I manage to get it into recovery and fix this I will let you know how

so after further testing :
holding reset for 30 seconds: fail
holding power for 10 seconds: fail
holding power for 1 min: fail
holding reset and then power:fail
power then reset:fail
opening case to disconnect battery; FAIL soldered to the board/battery wtf ?
pinhole on bottom of case between usb and power port doesnt sync up with a reboot option

ro0ks said:
so after further testing :
holding reset for 30 seconds: fail
holding power for 10 seconds: fail
holding power for 1 min: fail
holding reset and then power:fail
power then reset:fail
opening case to disconnect battery; FAIL soldered to the board/battery wtf ?
pinhole on bottom of case between usb and power port doesnt sync up with a reboot option
Click to expand...
Click to collapse
ok well this was an counterproductive day
called Cs @ 1-800-421-1404
waited 45mins on a "20min" wait
talked to someone who informed me this was the wrong number to call for help with the tablet
called Cs @ 1-888-999-0987
"we are experiencing a high call volume at this time, leave your name # and model number and we will return your call before the end of the business day"
waited until 3pm and called again finally got to talk to someone and it was horrible
I was initially told to press the reset button on the back, when I informed them that was not the issue. I was told to email [email protected] and detail my problem, after around 10mins of this, I was put on hold where 3 different ppl picked up and re-asked my problem. Finally when I asked to speak with a supervisor I was told he wasn't there.
When I explained that this is not uncommon in tablet from time to time, ppl forget what they used as a lock code, or one of their children played with it and put a passcode on the device. I was informed that they cant give me any further information because pioneer hired them to field tech support questions and they aren't part of pioneer. The whole reason they cant just tell me how to boot the device into recovery is they dont know, you see pioneer failed to give them that crucial piece of information.
supervisor is supposed to be calling me back tomorrow so lets see what kind of bs this is.
more then likely I will be de-soldering the battery leads from the board to force it into recovery tomorrow afternoon/

only thing I've found out so far thru trial and error is :
power on ,hold power till first logo, press reset and hold. 3-5 seconds later screen flashes white once (either turning on or off)
tablet off, insert usb connected to pc, rapidly tap power and it will stay on the charging screen , pc then recognizes device as libusb-win32 device "Worldcup device"
still no recovery mode

ESI is actually responsible for the tablet as pioneer leased out their logo for the tablet.
This is why there is a ridiculous run around trying to get help from pioneer's cs reps,ESI got my problem sorted.
look for a stock rom dump soon.

so what files would be needed exactly....
so far I have :
aml_logo.img
boot.img
bootloader.img
cache.ext4.tar
data.ext4.tar
logo.img
recovery.img
and still have to copy over system.ext4.tar

packaged rom file!
ok so after following this thread :http://forum.xda-developers.com/showthread.php?t=2195858
I ended up with this Pioneer r1 stock rom , anyone who has a stuck pioneer want to try ?

ro0ks99 said:
ESI is actually responsible for the tablet as pioneer leased out their logo for the tablet.
This is why there is a ridiculous run around trying to get help from pioneer's cs reps,ESI got my problem sorted.
look for a stock rom dump soon.
Click to expand...
Click to collapse
Hi, can you tell me how you solved the password issue and not able to get to factory reset. thank you.

There is no recovery mode , need to return tablet to ESI

ro0ks99 said:
There is no recovery mode , need to return tablet to ESI
Click to expand...
Click to collapse
I've been doing some searching myself, since I've got a soft-bricked R1 (Father-in-Law didn't want it any more), and from the looks of it, reflashing AML8726-based tablets is done via a rescue-SD card, or using a manufacturer produced USB burning tool:
http://www.slatedroid.com/topic/41478-how-to-unbrick-your-amlogic-aml8726-mx-series-tablet-v20/
So it appears that the tools are out there, but I haven't had any luck finding the device-specific files that will help.
I don't suppose you manged to find a way to contact ESI's technicians without going through the support number?

There is a recovery mode i unbricked mine just a few day ago need help finishing it it's very unstable
Sent from my SM-N900T using XDA Free mobile app

Could sort of get mine to boot...
My r1 crashed while watching a video and when I tried to restart it was stuck on this pioneer loading screen. I noticed if i let the battery run all the way out I could then get it to load up... but was greeted with dozens of error messages. This program has stopped this program has stopped. Every two seconds another error so trying to get on to google play for a scandisk app was pointless. I chose to restart and... back to Pioneer loading screen :/

Anyone ever locate a stock recovery flash for this tablet? TBT-7R1-P can be flashed via adb and ImageBurnTool. I have 2 tablets that 1, I do have CWM installed but need to connect a mouse to navigate (using a usb mouse plugged inthru an OTC cable) and nothing to restore since I'd wiped it.

Related

Brand new WM 6.0 phone won't turn on :(

I am about to burst out in tears
Oh yeah, Hi, my name is sitnet, I just registered.
Today I bought a HKC Mova 305 windows mobile 6.0 phone. You won't know the make, it is a local service provider make. It doesn't have any warranty, it was on promotion for very VERY cheap.
This is the problem:
When I turn it on it just shows the logo of the service provider (a splash screen) and then the screen goes dark (logo still visible in sunlight), but it doesn't do anything from there on. So then I did a soft reset (with a small reset button) but still the same thing.
Then I started experimenting, the phone has a load of buttons, there is a wheel on the side with a button below it and then also a camera button. I held in the button under the wheel and the power button together then this menu came up:
Code:
PB Update!
Connecting ...
INFO: Trying to initialize USB RNDIS...
HostMiniInit:: !!
Rndis:: initialization: with addr-0
Rndis:: initialization!
Rndis:: PDDInit success!
Rndis:: Get MAC address 4500,5634,9A78
Rndis:: initialization: Fail!
ERROR: Failed to initialize Bulverde Rndis USB Ethernet controller.
ERROR: Failed to detect and initialize Ethernet controller
Then I removed and reinsterted the battery and pressed the wheel button in while pressing the power button and got this menu:
Code:
------------------------
Xloader Version:
Eboot Version: Eboot-1.02-02
1(W): Update with SD Card
2(T): Boot from IPL KITL disable
3(B): Doc Update
4(L): Format Partition
5(R): Test Memory
-----from oallog--------
Enter your selection:
The buttons associated with the selections do not do anything though, BUT I experimented that I can select any of the options (except nr.4) with other buttons.
Ok and lastly when I press the Camera button and the power button together it says "KITL enable" and then only shows the splash screen again but forever.
This is my very first Windows mobile phone. I have no clue what to do
I have read that there is a way to reinstall the rom or something. I will do anything to get the phone working.
Here is the phone: ucables.com/ref/TELKOM-MOVA-305-PDA-P-R105795
Please, please I beg of anyone to help me, I will be so grateful it can't even be described in words.
EDIT: OK I found out that when pressing the "red dot" button (it changes between numbers and letter while typing) and the power on button it says waiting for USB connection and then I plugged it in and it installed as a "pocketPC" and now it says "Updating" on the screen. I'm just going to wait...
THANX so much guys!!!
Did you manage to get the phone booting. I`ve got the same problem with a phone I got today.
Kind regards
Got a link that might help. Haven`t tried it yet: expansys.jp/ft.aspx?k=119230
PS: Another name for the mova 305 is UBiQUiO 503G
ive got the same problem with mine...let me know if there's any changes
I found a link that will help. My phone is loading into windows mobile now. Not hanging on splash screen.
Good luck
expansys.jp/ft.aspx?k=119230
just add www to the front of the url. Wasnt able to post full link.
Thanx for the reply, i tried that method and could actually install that rom on the phone through the "super rom update" utility.However, when the phone restarts it still does the same thing...It just shows the telkom logo for 4 seconds then the phone switch off.
Any suggestions?
Thanx
So, somebody is trying to sell this phone again! And with the same useless initial rom in it as I can see!
The same support site has a new version of the rom that is 3.05 instead of the 2.2 here
Originally they were selling this phone with an extra special cable just for flashing the radio part of the rom but as far as I know it is no longer offered.
I think there is someone from China that posted on the same site that he's flashed WM6.5 on it but the guy disappeared! See here.
There is also more info on the Modaco website and an even a new rom! You will need to flash the 3.05 first then the 3.10 at Modaco. It is new but it is only a 6.0 rom but it addresses issues that people had with the phone. The Modaco website has more info about this phone.

Need To Restore Nexus S 4g

I have an extreme problem with my Nexus. I've been through thick and thin with this phone, and I'm hoping you guys will help with a solution to this problem.
The power button to my Nexus is broken completely. I stabbed it so much that the clicking black part is completely removed from the slot (on the motherboard).
One time, my Nexus S died, and I realized I had no way to turn it back on. I tried every single method (battery pulling, button pressing, USB connecting, etc) with no answer. I finally was able to find a solution. I used Odin to restore the bootloader tar md5 file, and thus auto rebooting the nexus (when the box is checked). This worked like a charm, until I realize I made a fatal mistake.
I chose an md5 file for the ORIGINAL Nexus S (not 4g).
I was able to easily go into recovery with Quick Boot from the Play Store. I installed Raspbean Jellybean (02-05-13 build), but the installation was very faulty. The home button is nonfunctional (it vibrates when pressed, but nothing happens) and Browser is not working as it just closes itself instantly. Like an idiot, I didn't install Gapps before rebooting into the ROM.
Stuck in that dilemma, I used the built in email app to sync my Gmail account to the phone. I sent a Quick Boot APK to myself to try and open so I could reach recovery, but it said there's no type of program that can open that file (maybe because Gapps isn't installed).
The last thing I tried was Odin again. I tried to restore the ICS release keys, but Odin will not recognize my phone anymore for nothing. I tried 3 different USBs (2 with shorts, and 1 normal one. I don't know if the type of USB has anything to do with it). Nothing.
So here I am with a faulty, Gappless ROM on my Nexus S 4G with a completely broken power.
I'm wondering if you guys have any solution/suggestion to get Odin to recognize my phone again so I can restore it and work from there.
Apart from that, ANY solution to this problem is highly acceptable and greatly appreciated (ways to get into recovery, etc). I don't want this to be the last of me and my sweet ole Nexus =(,
Thanks x1000 XDA!
Hey Guys. I was actually able to reach recovery, because the ROM I'm using has a Power Menu widget in it's quick settings (Go Figure). But my phone is still unable to be recognized by Odin in Download mode. The phone is also not recognized by my pc at all. It only charges, no matter what USB I try. I even tried mounting in recovery, no go.
Please help. Thanks!

[Q] MK808B won't start after plugging ubuntu pendrive

Hi,
First of all, great site you've got there, been checking it ever since I laid my hands on my first htc g1.
Secondly, and I hope I'm not double-posting about an issue already raised, as I've screened the threads quite thoroughly.
Here's the issue I have with my MK808B.
I've tried to start it with a USB ubuntu pendrive plugged into the USB OTG (I had saved some files I wanted to transfer, didn't realize it would mess things up).
Regular start up with this hdmi key is Google tv screen > android screen > home screen.
I get stuck at android screen, no matter how long I wait.
Out of nowhere, I tried to use another 2A power supply, as this had been advertised on other threads, no sucess... I also tried to start it with a paperclip pressing the reset button, didn't work...
Honestly, I don't know what to do exactly, I think it might have tried to boot ubuntu out of the usb stick...
I think I have no option left but to flash it (thus losing all that is installed already on it).
Is there any trick that could restore things the way they were? Any suggestion welcome.
Thanks for your time and help.
Solved by flashing
Hi,
Since no mgic trick happened to save the day, I was left with no choice but to flash it.
Used rockchip batch tools, crossed my finger so the stick wasn't a clone with the mediatek chip, flashed stock plus goodies rom, waited 10-15 minutes, and voila!
good as new, got rid of the chinese apps I couldn't even log on, but got a full wipe of my data.

Minix X5 Boot Problem

First post but have been reading this forum for a long time. This be the first time I have ran across an issue that has not been covered already on this forum or really any other. So here's the issue(s):
I have a stock X5 that is stuck on the Minix boot screen. I've made no attempts at modifying this device. This happened after watching some shoddy torrents of Breaking Bad. I had been noticing significant lag with the device prior to the downloads. Nothing other than standard media, social networking and gaming apps installed......there is a task killer on the device, the name escapes me at the moment.
Here's what I've tried:
1. Unplug all external devices (keyboard, external hard drives and removed SD card) and power up. Boot issue remains.
2. Unplug (then replug) power supply and start. Boot issue remains.
3. Hold reset button with pin and power up. DROID laying down with red triangle and exclamation comes up for a minute or two then it goes to the indef boot screen.
4. Held in reset button, power button and had girlfriend plug in the device. (I had no delusions of this doing anything but it stopped the gf's nagging to get it fixed for a while. I'm an electronics tech.....apparently that is the same thing as a programmer in her eyes.)
5. I've left the boot screen on for about 48 hours. Obviously this didn't fix anything.
6. Hooking the device up to my Samsung 7.7 tab. It turns on Android debugging on my tab but I really had no idea where I was going to go once I connected the devices. I just now thought of this and am planning on exploring this option a bit more with some searches. I'm quite sure there are no guides for working with these two specific devices though.
Hooking up to a computer to deal with recovery is not an option for me. I am not in the US and access to computers (other than an Internet cafe) is not an easy task. I am going to bet this is the best fix for most though.
My tab is rooted running PAC ROM if that is worth anything. This is currently my only real option for hooking up to another device. Hope to get some ideas here.
Hmm, so no one has any ideas? If using a comp is the only way can someone post how to recover an X5?
Jammertech said:
Hmm, so no one has any ideas? If using a comp is the only way can someone post how to recover an X5?
Click to expand...
Click to collapse
In case you didn't know, there is an (un)official Minix forum. May be they can help. (link)
Also, SomeCoolTech in YouTube has done a video on how to flash Minix X7. That could also be helpful.
Thanks for the reply. I was able to find someone to let me borrow their computer. Flashed the Finless ROM and it got it running again. The thing is not running smoothly though.
I had all kinds of issues then sent it in for rma, new x5 works perfectly, that is likely your best option. could you elaborate on your specific issues I am curious?

Hard Brick (possible hardware failure)

I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
WildZontar said:
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
Click to expand...
Click to collapse
Plug it into your computer, or a wall outlet with the battery out. See if it mounts as a strange drive or the led light flashes for a second.
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
WildZontar said:
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
Click to expand...
Click to collapse
At least it isn't completely fried, this method should work:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure it has no other sign of life first.
If you were on 4.1 then make sure you don't use a 4.3 file and lock your phone. Might have to do some digging around to find them, but they are around here somewhere.

Categories

Resources