First things first, DO NOT POST UNLESS YOU KNOW WHAT YOU ARE TALKING ABOUT!
Sorry, but telling me simply stupid responses will only annoy others who may be in the same situation while they are reading this and it will annoy me as well.
So this brick is highly complex and I hope someone knows what to do here. I have NvFlash enabled with the blob.bin, followed the guide here and check out this thread as it is highly similar to mine in the beginning. I see flumpster seems to know quite a bit, I hope he is still active on forums . So if I do the normal wheelie --blob.bin, it stops at
Code:
[+] Sending bootloader...
If I do the wheelie -r --blob blob.bin
Code:
Sending file: 100 %
Although this time the pad goes to the "Eee Pad" screen with the "Entering NvFlash recovery mode . Nv3p Server". and the chip uid.
I've tried two different computer both running Windows 7 64-bit and one of those also booted into its main operating system Ubuntu 12.10 64-bit. All with the exact same results. Terminating wheelie in with "-r" results in NvFlash just hanging at "[Resume Mode]" if I try to continue the process of unbricking. Before all this I used option 1b in this guide after a bootloop started after my tab crashed while playing a game. I hope someone can help me
Anyone know what to do, I don't want my thread to disappear into oblivion
It's been so long and not a single reply . I'm just going to weekly bump this and hope that at least one person knows what to do. :fingers-crossed:
I'm just gonna bump again in hopes that someone on this forum can help.
Suggest you start your post again with a better sentiment, It's pretty obvious why you have had no replies. Ask a mod to close this one and try to start your new one with a nicer tone
sbdags said:
Suggest you start your post again with a better sentiment, It's pretty obvious why you have had no replies. Ask a mod to close this one and try to start your new one with a nicer tone
Click to expand...
Click to collapse
Looking back at my OP I now realize that it did seem a bit mean although looking at other threads they often get flooded with obvious things. Sadly my brick needs someone who is a complex understanding of wheelie and nvflash. I think I'm going to try and get in contact with the AndroidRoot team.
Related
Hi all,
I have the HTC X7500 (unbranded) version. I have upgraded to WM6 several weeks ago using the method described on the forum (unlock by "IMEI check" then upgrade using ATHE100).
(on the bootloader I have:
ATHE100
IPL-v1.00
ATHE100
SPL-v1.10.RP00)
Today I tried to hard reset my device:
- I hold the camera button and press "reset"
- I have the "press action to restore factory default"
- when I do so I get "press power key too boot"
- I press the power key and the screen goes black and nothing happens...
What is going wrong? What should I do?
Thank you for your help.
Silviu
silviu.h said:
Hi all,
I have the HTC X7500 (unbranded) version. I have upgraded to WM6 several weeks ago using the method described on the forum (unlock by "IMEI check" then upgrade using ATHE100).
(on the bootloader I have:
ATHE100
IPL-v1.00
ATHE100
SPL-v1.10.RP00)
Today I tried to hard reset my device:
- I hold the camera button and press "reset"
- I have the "press action to restore factory default"
- when I do so I get "press power key too boot"
- I press the power key and the screen goes black and nothing happens...
What is going wrong? What should I do?
Thank you for your help.
Silviu
Click to expand...
Click to collapse
I won't flame you but the answer should be in the manual and is also all over the forum. Take this moment to teach yourself how to become more resourceful and find answers and become a better forum member. Good luck.
Also, to answer your question as to what you should do....read a little more as you'll need to be more knowledgeable with the device you have.
Hello,
Thank you for your reply (and for not flaming me ). I have managed to get it working again by flashing a Windows Mobile 5 ROM (by mistake) and then the Windows Mobile 6 again. However I still do not understand what exactly went wrong, why it works again now and what will happen next time I hard reset.
I had already read a lot of posts on the forum, however the learning curve is steep, and there are a lot of things to understand which are rarely explained from the ground up (most of the time the learning process must be made by assumptions and by inferring from what problems others have and how they solved them). And quite understandably I don't want to experiment too much with my device, especially when I read solutions that worked for other devices (like the Universal), and that might or might now work for mine.
Anyway, it's a shame that one has to become a PocketPC boot process expert in order to get out of such a situation, especially if one got into it without doing anything stupid (which I think is my case).
As a UNIX administrator and hacker I do know the power of RTFM, but I don't think it applies to each and every question.
Regards,
Silviu
silviu.h said:
Hello,
Thank you for your reply (and for not flaming me ). I have managed to get it working again by flashing a Windows Mobile 5 ROM (by mistake) and then the Windows Mobile 6 again. However I still do not understand what exactly went wrong, why it works again now and what will happen next time I hard reset.
I had already read a lot of posts on the forum, however the learning curve is steep, and there are a lot of things to understand which are rarely explained from the ground up (most of the time the learning process must be made by assumptions and by inferring from what problems others have and how they solved them). And quite understandably I don't want to experiment too much with my device, especially when I read solutions that worked for other devices (like the Universal), and that might or might now work for mine.
Anyway, it's a shame that one has to become a PocketPC boot process expert in order to get out of such a situation, especially if one got into it without doing anything stupid (which I think is my case).
As a UNIX administrator and hacker I do know the power of RTFM, but I don't think it applies to each and every question.
Regards,
Silviu
Click to expand...
Click to collapse
I don't believe you have to become and expert to get out of JAMs, however I do believe you better understanding what you are doing before you start flashing your phone or device with something not released by your phone Operator.
Keep in mind you got yourself into that situation when you decide you are going to unlock your phone (play with the BIOS) and flash it with a WM6 ROM (Unsupported OS). Being a Unix Administrator, how often do you play with an Ultrasparc BIOS then decide to install an unsupported version of Solaris on it.
Nonetheless the Windows Mobile device does not cost as much and it would only affect you if you bricked it. The point I am trying to make here is that what we are doing with these phones are pretty serious and if you choose not take baby steps and read carefully, then you better be prepare to purchase new device and deal with the outcome.
I am not flaming anyone, but I think people needs to understand this is serious and the Athena is not $49.99 or free with a two year contract
Mayby my post will help a little.
First : you have to have battery charged for 100% ( my a few upgrade stopped in booting proces after upgrade because battery was on the level 70% ) So try to made HR with unit connected to power charger ( not to USB in PC)
Second: Try to go BL mode , if yes you can upgrade again, try it few times
Third : Last solution is to boot in BL mode with miniSD card with Atheimg.nbh on it , the same you have try few times
As up today it helps me.
Hello,
Thank you for your help but I said above: "I have managed to get it working again by flashing a Windows Mobile 5 ROM (by mistake) and then the Windows Mobile 6 again." So things are OK for me
Besides, since then I have flashed to HardSPL, and hard-reset seems to be working OK now.
Thank you anyway and long live the forum
Silviu
EDIT: Well I managed to get clockworkmod installed and everything; still having some issues with aspects of it, but in general I'm good. I'll probably make a dedicated thread to the device; if anyone wants to suggest a proper forum section, be my guest.
Ok, so I need some assistance on installing CWM or another recovery mode on my YourPad P4. I've already rooted and installed ROM Manager, but it could not find a compatible CWM version.
Now, first off I have also been unable to get an exact or better identification of this tablet other than it being sold as a "YourPad P4" and that it's model is MID; so I might also need help getting more details to better assist the finding of a compatible or working recovery.
Here is some information about it...
* Site purchased from/detail page:
http://www.yourstoreonline.net/yourpad_p4_new_android_40/id2040716/product.html
Don't worry, I got it for ~$100 (with the 1GB RAM upgrade), not the displayed price on the site!
* About tablet page info:
Model number: MID
Android version: 4.0.3
Kernel version: 3.0.8
[email protected] #2
Build number: 20120807-A721
Also, before I start messing with it I was going to make a nandroid backup to share for others...does nandroid backup firmware as well? I've never needed to restore a backup so I have no idea what goes into it and can't find a quick answer. I'd like to make a backup of a clean as possible system to share for anyone wanting it. Although I'm surprised that its not been mentioned on xda, I'd expect this tablet to have at least been asked about once considering it was mentioned on woot.
Thanks to anyone for any help, and I apologize if this should be in a different section. If so, could a mod please move it before any fuss is made.
And now, I'm off to bed (so I won't be responding/checking this for a few hours).
Not to sure about the rules for thread bumping, but I just wanna make sure this gets seen soon (as I'll be very busy and it will be hard to work on it next week and the the days that follow).
Also I thought it was worth mentioning now that only really mentions of this tablet I can find are in posts by me, ahahahahaha
EDIT: Oh, and I havn't verified I even have a recovery partition yet as I can't cat /proc/mtd
it's been about a week now and no response; I even posted it over here http://www.androidtablets.net/forum...cs-need-help-recovery-install-yourpad-p4.html
so bumping, if anyone at the very least knows some mystical other worldly site that somehow manages the chance of providing me an answer over the ever amazing xda; please post
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
AJ88 said:
tabletrepublic.com/forum/iview-760tpc-ployer-momo9/iview-760tpc-k-ployer-momo9-firmware-rom-releases-1610.html
Go here you will find all about all winner a10 tablet
Just go there and for cwm recovery 5
Select
3.) ClockworkMod Recovery
5 (for AllWinner A10 tablets) option.
Just read all step carefully
And do at your own risk me or xda is not responsible if you brick your device..
we all should be polite enough to press thanks for anyone who helped US.
Click to expand...
Click to collapse
Thanks alot for this, I'll definitely read it over a few times before attempting. Hopefully this will work out. Thread is still open for any other input, so anyone else coming here that can provide any additional help go ahead and post.
Well I still have been unable to get a recovery option going. I tried the link mentioned by AJ88 and it didn't work for me. Essentially the link boiled down to 2 simple adb commands and a custom recovery.img. First step was to "adb push recovery.img /data/", but I ran into a permission denied issue and could not figure out a way around it (didn't want to mess with chmod, but I did run the "fix permissions" script in the clockworkmod rom manager. So instead I just pushed the recovery.img to my sdcard. Next step was "adb shell "cat /data/recovery.img > /dev/block/nandg; sync""; so instead I went "adb shell" then su to make sure I didn't get any more issues, then just "cat /sdcard/recovery.img > /dev/block/nandg; sync". Rebooted and tried all combinations of key pressings to access recovery with no luck (even tried via adb). So any ideas on my next course of action?
youtPad P4 issues
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Well I've been waiting for a reply to either of my threads with no luck, so today I figured I'd just try again the method of manually setting up a recovery, and this time I just decided to try and hold every button I could while powering and and BAM RECOVERY MODE *****ES!!!!!! So guess either I must've just screwed up last time or something. Anyways, I'll edit the OP to reflect all this later...maybe start a dedicated thread with any quirks I figure out down the line using this tablet; and of course post my nandroid backup. When I setup my 2nd YourPad, I'll make sure to make backups of any files I may have had to change (ie, nandg, etc). The question is, what section would such a thread belong?
5lita5 said:
Dear EarthBoundX5,
Please do not feel alone in what I might be perceiving as "buyer's remorse" as I also own this device and have begun to have issues with it functionality. Initially I was attracted to this device for what seemed a myriad of available functions and abilities, however I'm really starting to believe the old saying, "you get what you pay for".
My main issue at this point is when using the free Kindle app, after selecting my book, the screen goes completely blank and does NOT come back with the reading material I've selected. If I touch the back button, I get a brief flash of the screen showing the page that I'm on in the book, but after that nothing. I've tried rebooting the machine, currently trying a fresh install of the Kindle app, we'll see how that goes TODAY.
I also have another off-brand tablet, iBridge, which was purchased during the frustration period of waiting for YourStore . com to get their act together and send me the YourPad. Funniest part about it though is that the iBridge comes with a booklet thats 4x the size of the poorly written "booklet" that the YourPad people put out.
I'm sorry that I don't have a solution for your problem as I'm a complete newb with the tablet world, but wanted to at least touch base with you to let you know "you are not alone. I am here with you...." LOL
Found you with a google search for online help regarding YourPad, and it brought me to you, and this seems like the most helpful place I might have found in reference to oddball tablet issues. Take care, have a good day. and I'll check back in to notify regarding Kindle reinstall.
Click to expand...
Click to collapse
I don't feel any buyer's remorse...yet at least, haha. If I end up having the same issues as you, maybe I'll change my mind; but I really don't see much wrong yet with this tablet. I mean, obviously its cheap and all, but for the poor man its fantastic. But ya, I HATE the YourStore, they took FOREVER to ship out the tablets. Anyways, for people like you, it really makes me thing I should take point on this tablet and start a dedicated thread.
I have done a fair amount of research with my problem and would not post unless I was at wits end. So I made a terrible mistake and formatted my phone and took off my back ups. So after researching the problem I learned how to use ADB to either push or side load. Unfortunately my driver for my G2 is not present, and I have had no luck updating it. The device ID presently is USB\VID_18D1&PID_D001&REV_0232
I feel there is most likely an easy fix for my problem that I am overlooking but after hours of trial and error I am now completely out of ideas. My question is simple; how do I fix my driver.
Any help or suggestions would be much appreciated.
There is hope!
Denux2k10 said:
I have done a fair amount of research with my problem and would not post unless I was at wits end. So I made a terrible mistake and formatted my phone and took off my back ups. So after researching the problem I learned how to use ADB to either push or side load. Unfortunately my driver for my G2 is not present, and I have had no luck updating it. The device ID presently is USB\VID_18D1&PID_D001&REV_0232
I feel there is most likely an easy fix for my problem that I am overlooking but after hours of trial and error I am now completely out of ideas. My question is simple; how do I fix my driver.
Any help or suggestions would be much appreciated.
Click to expand...
Click to collapse
I have a sprint G2 Rooted with TWRP I couldn't for the life of me get ADB working when i bricked doing an OTA. Go to this link and follow instructions EXACTLY!!! This is the only thing that saved my G2... let me know...
http://forum.xda-developers.com/showthread.php?t=2432476
Okay, so I apologize in advance if this cannot be posted here. My reason for doing so, is because I need some help with a Zenwatch 2 by Asus and the thread pertaining to this device seems to be a ghosttown. So if you need, please move this where it should go, but not without offering a word of advice or two first
So obviously I have a zenwatch 2, and I was tinkering with it earlier, and somehow got it stuck in CVC fastboot or something like that. I was able to get TWRP on it (Thank god, im much more optomistic now) but I am still having trouble getting an OS back on it. At first I wasnt even able to read the internal storage from my computer, or even begin to sideload anything, but I went into the TWRP settings and repaired the partitions to EXT4 or something of that sort. Now I am able to sideload, as well as access the storage from my PC, but I have had no success in flashing a working OS.
Im usually pretty familiar with android, rooting and unlocking, but these watches seem to be a bit different.
If anyone has anything that would help, please feel free!
The exact model of watch I have is WREN W1502Q .... I think.
Thanks in advance!
UPDATE:
I got it to boot!! Now I am stuck with a hang on that screen with all the swirly dots (the four separate animations that is right before boot)
So we're making progress, but I dont know if it is just gonna take a long time to boot, or if it is hanging! Hopefully we can get over this last hump. Thanks!
UPDATE 2:
Back up and running!
Praise the Lord!
Hey all,
I've never rooted a phone before so since I have a spare model, I figured I'd give it a go.
Hearing about this forum, I checked it out and was sent to the Sony site. I understand I needed to unlock the bootloader first, which I did and can confirm I get that alert as my phone starts about it not being safe.
Hint for future readers: don't do this in a virtual environment, I had issues doing this until I used an actual computer and not a VM (mods and folks with more experience: feel free to correct me on this or shed some light). To be clear, I have a separate host running Proxmox (Type I hypervisor) and was able to forward my USB connection to test with ADB and such. I do most things in a virtual environment to not mess up my physical computer.
This was all done last week. Well today, Monday, I decided to continue with my rooting excursion, only to run into the issue I am currently facing.
After many, many Google attempts and following whatever links in this, I finally found this link. Well, I was within a VM, downloaded the linked flashing tool, and ran the first two commands:
- adb devices
- adb reboot bootloader
After doing this, my phone turned off and I wasn't sure what to expect, so I pressed the Power button to see what would happen - nothing. So then I remembered that Friday I was having issues communicating with my mobile phone in the VM to unlock the bootloader in the first place, so I figured I'd try to move it to my physical computer....then I was stuck on a reboot cycle!
To be clear, my issue is that I am stuck on a boot loop. It prompts the error of the device being unsafe, waits 5 seconds, then displays the Sony splash screen. Rinse, wash, repeat; same thing.
I have a Sony Xperia XA1 (G3123) model.
Can anyone shed some light?
Am I screwed?
Please halp!
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
tryingToSurvive said:
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
Click to expand...
Click to collapse
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
keifus.rahn said:
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Hey @keifus.rahn for following up.
I did find that thread after continued poking, which I am still checking now. And I eventually made a post on there just now discussing my current dilemma.
I downloaded the Flashtool but didn't understand how it worked, nor do I still yet. I tried debugging it and the issue is that the "java -version" call doesn't work within the directory's own structure. I do have java installed on my test Linux VM though.
Past that, I tried with the latest boot.img as well as the recovery.img that I found. I think that the build numbers are off, or maybe I am just not understanding where I am lacking.
You can look at the bottom of the last page for a breakdown of what I did:
https://forum.xda-developers.com/xa...21-built-sources-t3622886/page94#post80481385